#9322 [FS Integration] SVCITEM-CUSTASSET mapping ignores "Convert to Customer Asset" flag — every Service Item synced to FS unconditionally
Field Service Integration now respects the Dataverse Product setting Convert to Customer Asset when syncing Service Items, preventing unconditional synchronization unless the flag is enabled or records are already coupled.
- 4files
- 2AL files
- 2objects
Pull request · merged into main (BC30) on 2026-07-15 by tomasevicst · 4 files (+158 -0), 2 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Service Items are now filtered based on the Convert to Customer Asset flag in the linked Dataverse Product
- Already-coupled Service Item/Customer Asset pairs continue syncing regardless of the flag to avoid disruption
- The fix exposes the msdyn_converttocustomerasset field and adds post-filter logic to OnQueryPostFilterIgnoreRecord
- Service Items without Item numbers or uncoupled Items are not blocked by the new filter
- Automated tests cover filtering behavior for enabled/disabled conversion and edge cases
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 6610 “FS Int. Table Subscriber”, FieldServiceIntegration: modified
- Table extension 6617 “FS CRM Product”, FieldServiceIntegration: modified
Context
- Work items: AB#640250
- Labels: AL: Apps (W1), Team: SCM
- Systems: integration
- From the description: “Service Items were synced to Field Service Customer Assets without honoring the Dataverse Product setting Convert to Customer Asset.”
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).