Attachment Base64 to get Base64 of an attachment and the file details.

[anveshmupparaju]

This action provides Base64 string of attachment which is useful for transmitting attachments over integrations. This action accepts sys_id of attachment as input and provides Base64 string as output if everything is successful. Otherwise Error will contain the error string.

[rohi-v]

Thanks for your submission. It appears that this pull request contains more files than described in the title. Please review and update the pull request to either remove the extra/unintended files or to update the description to be more comprehensive. Ensure your contributions are meaningful and adhere to the project’s standards. [If applicable: You can create a new branch on your forked repository to avoid accidental inclusions of new commits in the future.]. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

[SapphicFire]

Hi @anveshmupparaju. When you committed your action to source control, it appears that 39 extra files (sys_documentation & sys_choice records) were included, as well as updates to the other actions in the instance. Were these files listed in the commit window? If you were to create a new branch based off of main in your fork, do you see the same behaviour?

I am keen to identify what has happened so we can get this sorted - This is a great contribution 😁

[anveshmupparaju]

@SapphicFire I did a fresh fork and performed the same action and I saw the same behaviour.

Let me try again and get back.

[SapphicFire]

Your attachment_base64_v2 branch is created based off of the attachment_base64 branch, not off of the main branch in your repo. You can either create a new branch in github, or switch back to main in your instance and then create a branch in Studio