#10748 [SOA] Resolve the current agent's setup instead of an arbitrary one
The Sales Order Agent now resolves its setup configuration through the current session identity instead of reading arbitrary setup records, ensuring each agent instance uses its own settings for item search and availability filtering.
- 5files
- 5AL files
- 5objects
Pull request · merged into main (BC30) on 2026-08-28 by qasimikram · 5 files (+30 -13), 5 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Added GetForCurrentAgentSession() method to SOA Setup table to retrieve the setup belonging to the current agent session
- Fixed item search and availability filtering to use the correct agent’s configuration instead of arbitrary setup records
- Updated upgrade routines to iterate all setup records instead of only the first one, ensuring every agent receives configuration updates
- Eliminated inconsistencies where different code paths read different setup records during single operations
- Session identity-based filtering aligns this with patterns already used by other SOA components
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 4589 “SOA Upgrade”, SalesOrderAgent: modified
- Page 4410 “SOA Multi Items Availability”, SalesOrderAgent: modified
- Codeunit 4591 “SOA Item Search”, SalesOrderAgent: modified
- Table 4325 “SOA Setup”, SalesOrderAgent: modified
- Codeunit 4306 “SOA Session Filter”, SalesOrderAgent: modified
Context
- Work items: AB#647996
- Labels: AL: Apps (W1), Ownership: Manual, Team: SCM
- 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).