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 access to the Id field of the attachment in the “Email Message Attachment” table via the EMailMessage codeunit (8904) #2038

Open
1 task done
SPinkow opened this issue Sep 16, 2024 · 1 comment · May be fixed by #2186
Assignees
Labels
Approved The issue is approved Bug Something isn't working Integration GitHub request for Integration area

Comments

@SPinkow
Copy link

SPinkow commented Sep 16, 2024

Describe the issue

There is currently no way to determine the ID of an attachment that is attached to a mail. The ID is currently stored in the internal table 8904 “Email Message Attachment”. As the table is internal, you can only access the attachments via the codeunit 8904 “Email Message” and iterate over the attachments with the functions Attachments_First() and/or Attachments_Next(). There are other methods in the codeunit that can be used to access the name of the attachment, for example. Unfortunately, several attachments can have the same name so that they cannot be clearly identified.

Identification would be possible via the Id field of the “EMail Message Attachment” table. However, there is no function in the implementation codeunit 8904 that returns the Id. Such an addition would provide considerable added value in identifying the correct attachment of the mail.
I would like to add to the code so that this is possible in the future.

Expected behavior

I would expect to have a method available via codeunit 8904 “EMail Message” that returns the ID of the current attachment.

Steps to reproduce

As you can see in the screenshot, you can access some methods in the codeunit, but the ID of the attachment remains internal.

image

Additional context

No response

I will provide a fix for a bug

  • I will provide a fix for a bug
@SPinkow SPinkow added the Bug Something isn't working label Sep 16, 2024
@JesperSchulz JesperSchulz added the Approved The issue is approved label Sep 24, 2024
@JesperSchulz
Copy link
Contributor

Sounds reasonable! Approved.

@JesperSchulz JesperSchulz added the Integration GitHub request for Integration area label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved The issue is approved Bug Something isn't working Integration GitHub request for Integration area
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants