BC Observatoryunofficial, made by waldo
code change · featureInventoryofficial - Microsoftreviewed - checked by Opus

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

A new integration event allows extensions to influence whether item variant rows are printed in the Item Sales Statistics report when "Only Items with Sales" and "Breakdown By Variant" are both enabled, by exposing the skip decision and related data to subscribers.

Open in Claude9774.mdPull request #9774

Pull request · merged into main (BC30) on 2026-08-27 by AleksandricMarko · 1 file (+12 -6), 1 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • New event OnItemVariantOnAfterGetRecordOnBeforePrintOnlyIfSalesCheck fires after Item.CalcFields and before the skip check in the Item Variant OnAfterGetRecord trigger
  • Event parameters expose Item, ItemVariant, and the PrintOnlyIfSales flag to subscribers
  • Extensions can override the SkipRecord variable via a var parameter to fold in their own sales figures
  • Solves the issue that extensions could not influence the row skip decision for custom sales quantities
  • Event raised at the variant level, enabling subscribers to control row visibility per variant

AL objects touched

Context

  • Work items: AB#644154
  • Labels: Team: SCM, event-request
  • Systems: inventory

Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).