[Extensibility Request] issue 30377: add OnBeforePrintOnlyIfSalesCheck event in Item Sales Statistics report - #9777
Open
AleksandricMarko wants to merge 1 commit into
Open
[Extensibility Request] issue 30377: add OnBeforePrintOnlyIfSalesCheck event in Item Sales Statistics report#9777AleksandricMarko wants to merge 1 commit into
AleksandricMarko wants to merge 1 commit into
Conversation
…Check event in Item Sales Statistics report Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
AleksandricMarko
marked this pull request as ready for review
July 28, 2026 10:00
AleksandricMarko
enabled auto-merge
July 28, 2026 10:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The report
10135 "Item Sales Statistics"calculatesSales (Qty.)viaCalcFieldsand, in the same trigger, decides whether toCurrReport.Skip()the record based on the privatePrintOnlyIfSalesflag before any extension code runs. Extensions that compute alternate-UOM sales figures cannot influence this skip decision becausePrintOnlyIfSaleshas no accessible getter and the skip happens before the table'sOnAfterGetRecordtrigger fires. This PR exposes the already-computed skip decision through a new integration event so subscribers can override whether an item is skipped, in either direction.Source issue repository: microsoft/AlAppExtensions; issue number: 30377
Changes Made
Report 10135 "Item Sales Statistics"- In theItemdata itemOnAfterGetRecordtrigger, the inlinePrintOnlyIfSalesskip check was factored into a localSkipRecordboolean and a new integration eventOnAfterGetRecordItemOnBeforePrintOnlyIfSalesCheck(var Item; PrintOnlyIfSales; var SkipRecord)is raised afterCalcFieldsand beforeCurrReport.Skip(), letting subscribers override the skip decision. Added the matching event publisher. Behavior is unchanged when no subscriber is present.Fixes AB#644155