[Extensibility Request] issue 30378: add OnItemVariantOnAfterGetRecordOnBeforePrintOnlyIfSalesCheck event in Item Sales Statistics report

[AleksandricMarko]

Summary

When "Only Items with Sales" and "Breakdown By Variant" are both enabled on the Item Sales Statistics report (10135), the base report decides, per item variant, whether to skip a row based solely on Item."Sales (Qty.)" and the private PrintOnlyIfSales flag. Extensions that compute their own sales figures (for example alternate unit-of-measure quantities) cannot influence this decision because PrintOnlyIfSales has no accessible getter and the skip is evaluated before any extension trigger runs. This PR exposes the already-computed skip decision through a new integration event at the variant level so subscribers can fold in their own figures.

Source issue repository: microsoft/AlAppExtensions; issue number: 30378

Changes Made

• OnItemVariantOnAfterGetRecordOnBeforePrintOnlyIfSalesCheck - new integration event raised in the Item Variant OnAfterGetRecord trigger after Item.CalcFields and before the CurrReport.Skip() check; the inline skip condition now assigns a SkipRecord boolean that the event can override via var, exposing Item, ItemVariant, and PrintOnlyIfSales to subscribers.

Fixes AB#644154

[AleksandricMarko]

@copilot
in local procedure OnItemVariantOnAfterGetRecordOnBeforePrintOnlyIfSalesCheck(var Item: Record Item; ItemVariant: Record "Item Variant"; PrintOnlyIfSales: Boolean; var SkipRecord: Boolean) paremeter Itemvariant should be with VAR

[Copilot]

@copilot
in local procedure OnItemVariantOnAfterGetRecordOnBeforePrintOnlyIfSalesCheck(var Item: Record Item; ItemVariant: Record "Item Variant"; PrintOnlyIfSales: Boolean; var SkipRecord: Boolean) ...

Fixed in the latest commit — ItemVariant now has the var modifier: var ItemVariant: Record "Item Variant".

[qasimikram]

S1 - Clearing SkipRecord here does not control the final decision: the same trigger later calls CurrReport.Skip when all standard quantity/value fields are zero. That is precisely possible for alternate-UOM extension sales. Move the publisher after the return calculation or expose the final skip decision, and test zero standard sales with nonzero extension sales.

S2 - The parent Item trigger can skip before the Item Variant dataitem runs, so this publisher depends on the companion item-level hook. Deliver the hooks together or otherwise ensure the variant event is reachable for the documented scenario.

S3 - Pass ItemVariant by value. Allowing mutation after SetRange and CalcFields can combine values calculated for one variant with a different variant code used by later logic.