Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Missing procedure to get the Data of a Email Message Attachment #3103

Open
1 task done
Erden-GOB opened this issue Feb 26, 2025 · 1 comment
Open
1 task done
Labels
Approved The issue is approved Integration GitHub request for Integration area

Comments

@Erden-GOB
Copy link
Contributor

Describe the issue

To find the "Tenant Media" entry for a specific attachment of a "Sent Email" you need the value of the "Email Massage Attachment" Data field. This field has a GUID which is the Primary Key of the "Tenant Media" table.

"Email Massage Attachment" is an internal table of the "Sent Email" subpage.
The "Email Massage" Codeunit for managing the table currently lacks a procedure to get this Data field.

In addition to already existing procedures like Attachments_GetName, Attachments_GetLength etc., i would like to add an Attachments_GetData procedure which then returns the Guid.

Expected behavior

A procedure in the Email Message Codeunit which returns the Data of the Attachment

Steps to reproduce

No procedure available to get the Data of an email attachment

Image

Additional context

No response

I will provide a fix for a bug

  • I will provide a fix for a bug
@Erden-GOB Erden-GOB changed the title [Bug]: [Bug]: Missing procedure to get the Data of a Email Message Attachment Feb 26, 2025
@JesperSchulz
Copy link
Contributor

I don't see why not. Approved.

@JesperSchulz JesperSchulz added Approved The issue is approved Integration GitHub request for Integration area labels Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved The issue is approved Integration GitHub request for Integration area
Projects
None yet
Development

No branches or pull requests

2 participants