Share
Report
69We are building a custom integration between D365 F&O and Dynamics 365 Sales (CRM) using Custom APIs. We decided not to use Dual-write to keep the integration logic simpler and more controlled.
In our F&O environment, we have two Legal Entities. I need to mirror this structure in CRM correctly to ensure:
-
Data Isolation: Users belonging to Legal Entity A should not see records belonging to Legal Entity B.
-
API Mapping: When a record is updated in CRM, the API needs to know which
dataAreaIdto target in F&O.
My question is: What is the most "Standard" and recommended way to handle this in CRM without breaking the native system logic?
-
Should I create a Business Unit (BU) for each Legal Entity to handle security and visibility?
-
Should I use a Custom Text Field to store the Company Code for API mapping?
-
Or is a Hybrid approach (BUs for security + Custom Field for API string mapping) the best way to go?
I want to follow the best practices for CRM architecture so that the system remains scalable and easy to maintain.
Has anyone implemented this scenario using APIs? Would love to hear your advice!
All responses (
Answers (
