This should be the same across all address fields in BC.
BC would need an Address 3 and field lengths to match CE & CDS
Comments
Per request from Ivan Koletic on Yammer, putting this here:Extend Match Based Coupling for Dataverse to allow constants Example:I have Accounts in Dataverse with 2 addressesI want Address 1 fields to integrate to Customer card in BCI want Address 2 fields to integrate to Ship-to AddressI can set up custom integration table mapping to map Account Address 2 fields to Ship-to Address record, using fixed value for Ship-to CodeI can't run Match-based coupling, as it only recognizes fields on Account record and does not allow constants.
Category: General
Inside Dataverse, the address registries could be segmented by column Address TypeThe Idea should create an Integration Table Mapping for each Type of Address needed on BC.Of course it should take into consideration the Company on BC to be filtered as It's done on Account Integration Table Mapping.
Category: General
Sorry, some of my references are outdated! I mean align to the Accounts / Contact entities in the Common Data Platform (CDP) and Dynamics 365 Sales, etc.
Category: General
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team