[Extensibility Request] issue 30429: add events to disambiguate CRM integration table mappings - #10578
Open
Onat Buyukakkus (onbuyuka) wants to merge 1 commit into
Open
[Extensibility Request] issue 30429: add events to disambiguate CRM integration table mappings#10578Onat Buyukakkus (onbuyuka) wants to merge 1 commit into
Onat Buyukakkus (onbuyuka) wants to merge 1 commit into
Conversation
…ntegration table mappings Adds four integration events so extensions can select the correct "Integration Table Mapping" when multiple mappings share the same BC "Table ID" (for example, a Sales Header mapping that syncs quotes alongside the standard sales order mapping): - Codeunit "CRM Order Status Update Job" (UpdateSalesOrders): OnUpdateSalesOrdersOnBeforeFindIntegrationTableMapping - Table "Coupling Record Buffer" (Initialize): OnAfterInitialize - Codeunit "CRM Integration Management" (RemoveCoupling): OnRemoveCouplingOnBeforeGetIntegrationTableMappingForUncoupling - Codeunit "CRM Integration Management" (MatchBasedCoupling): OnMatchBasedCouplingOnBeforeGetIntegrationTableMappingForMatchBasedCoupling RecordRef context parameters are passed by value (read-only) so subscribers can inspect the source record without mutating caller state. Fixes AB#647520 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4f698109-800e-4840-b9b5-603e3e682257
github-actions
Bot
added
the
Team: Integrations
Onat Buyukakkus (onbuyuka)
enabled auto-merge
August 24, 2026 22:45
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds four integration events so extensions can select the correct
Integration Table Mappingwhen several mappings share the same Business CentralTable ID— for example, aSales Headermapping that syncs quotes alongside the standard sales order mapping. Today the base code disambiguates only byTable ID, so extensions with additional same-table mappings can resolve the wrong mapping during order-status updates, coupling, uncoupling, and match-based coupling.Requested via ALAppExtensions #30429.
Changes
UpdateSalesOrdersOnUpdateSalesOrdersOnBeforeFindIntegrationTableMappingInitializeOnAfterInitializeRemoveCouplingOnRemoveCouplingOnBeforeGetIntegrationTableMappingForUncouplingMatchBasedCouplingOnMatchBasedCouplingOnBeforeGetIntegrationTableMappingForMatchBasedCouplingAll events are thin
[IntegrationEvent(false, false)]publishers.RecordRefcontext parameters are passed by value (read-only) so subscribers can inspect the source record to choose the mapping without mutating the caller's state, matching the existing input-onlyRecordRefevents in the integration sync engine.Fixes AB#647520