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

[Event Extension Request] Codeunit 44 - ReportManagement - Add *actual* Layout MIME Type + Layout Application ID #18941

Closed
rvanbekkum opened this issue Jun 30, 2022 · 2 comments
Labels
event-request Request for adding an event ships-in-future-update Fix ships in a future update

Comments

@rvanbekkum
Copy link
Contributor

Dear ALAppExtensions team,

Through this request we would like to request some properties to be added to the ObjectPayLoad: JsonObject parameter of the OnCustomDocumentMergerEx event of the ReportManagement codeunit, an event that is added in BC 20.2.

  1. Could you please have the layoutmimetype property contain the actual MIME Type? It will now always have "Application/ReportLayout/Custom" which is not useful. Preferably it should take the value from the "MIME Type" field in the report layout system tables, so that if there are multiple extension developers, we can easily check this value to determine whether our extension should handle the report rendering request.
  2. Please add a layoutApplicationID property to the ObjectPayLoad so that we can determine if a system-defined/extension-defined report layout or user-defined report layout is used, i.e., so that we know exactly which layout is used. The problem is that extension-provided and user-defined report layouts could have the exact same name, but it would be good to be able to determine which one the current rendering request concerns.

Thank you in advance! If you have any further questions or thoughts, please let us know as well.

@AlexanderYakunin AlexanderYakunin added the event-request Request for adding an event label Jun 30, 2022
@JesperSchulz
Copy link
Contributor

Availability update: We will publish a fix for this issue in the next update for release 20.

Build ID to track: 44550.

@JesperSchulz JesperSchulz added the ships-in-future-update Fix ships in a future update label Aug 3, 2022
@JesperSchulz
Copy link
Contributor

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Build ID: 21.0.44555.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
event-request Request for adding an event ships-in-future-update Fix ships in a future update
Projects
None yet
Development

No branches or pull requests

3 participants