#9225 [Extensibility][SubscriptionBilling]: Make usage data billing filtering extensible in SetUsageDataBillingFilters
Usage data billing filtering in Subscription Line now uses an open-ended filter instead of a bounded range, allowing custom enum values to be included, and adds an integration event to let partners adjust the filters.
- 3files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-09-17 by miljance (community contribution) · 3 files (+61 -1), 1 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Replaced bounded SetRange with SetFilter to include custom Usage Based Pricing enum values above the original maximum
- Added OnAfterSetUsageDataBillingFilters integration event for extensibility
- Behavior unchanged for existing shipped enum values (ordinals 1-3), None (ordinal 0) still excluded
- Custom partner-added enum values (ordinal ≥4) now included instead of silently dropped
- Low risk change with backward compatibility maintained
- Behaviour changes for users or extensions.
AL objects touched
- Table 8059 “Subscription Line”, Subscription Billing: modified
Context
- Fixes: #9223 [Extensibility Request][Subscription Billing] Make usage data billing filtering extensible for custom “Usage Based Pricing” enum values (closed)
- Work items: AB#647367
- Labels: ADO: Sync, AL: Apps (W1), From Fork, Team: Finance
- Systems: development
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).