Share
ReportHello Community,
I would appreciate some guidance on a Dual-write scenario.
I would like to synchronize existing CRM Sales Leads (Dataverse) with the Prospects entity in Finance & Operations, so that CRM Leads are automatically created as Prospects in F&O.
However, I am facing two main issues:
- The F&O Prospects entity contains fields such as
PROSPECTIDandmsdyn_fields, but these corresponding columns do not appear to exist in my Dataverse Lead table. - I receive the following error when configuring the mapping:
"Prospects or AX is a company-specific entity with primaryCompanyField set to DataAreaId and leads of CRM is a cross-company entity that doesn't have primary company field set."
My questions are:
- Is this integration between Dataverse Leads and F&O Prospects supported using Dual-write?
- How should the missing
msdyn_fields and theDataAreaIdcompany mismatch be handled? - Is there a recommended standard mapping or configuration for this scenario?
Any guidance or documentation would be greatly appreciated.
Thank you!
I have the same question (0)
All responses (
Answers (
307,003
