Share
ReportHello Everyone,
I am currently working on an end-to-end integration setup where my intention is to move data from Dynamics 365 Finance & Operations (F&O) → Dataverse → Azure Data Lake Storage (ADLS) via Synapse Link → Synapse Analytics / Power BI for reporting.
I am currently working on an end-to-end integration setup where my intention is to move data from Dynamics 365 Finance & Operations (F&O) → Dataverse → Azure Data Lake Storage (ADLS) via Synapse Link → Synapse Analytics / Power BI for reporting.
Using Dual-Write, I am able to see and sync the standard F&O tables/entities into Dataverse without any issues.
Problem:
The challenge I am facing is that custom objects created in F&O are not appearing in Dataverse, so I am unable to bring them over through Dual-Write.
Because of this, I cannot establish the full pipeline (F&O → Dataverse → ADLS → Synapse) for my required reporting.
The challenge I am facing is that custom objects created in F&O are not appearing in Dataverse, so I am unable to bring them over through Dual-Write.
Because of this, I cannot establish the full pipeline (F&O → Dataverse → ADLS → Synapse) for my required reporting.
Help Needed:
I would like guidance on the required steps to make custom F&O objects available in Dataverse through Dual-Write. Specifically:
I would like guidance on the required steps to make custom F&O objects available in Dataverse through Dual-Write. Specifically:
What must be done in F&O (Dual Write, Data Entities, Models) so that a custom table becomes dual-write enabled?
How to expose custom data entities to Dataverse (metadata requirements, build/sync steps)?
Any specific configurations or solution packages that must be deployed in Dataverse for custom entities to appear in the Dual-Write table mapping list.
Security or permission prerequisites needed on either side (F&O or Dataverse) to view custom objects.
Known limitations or extra steps for custom objects to flow all the way through Synapse Link to ADLS/Power BI.
How to expose custom data entities to Dataverse (metadata requirements, build/sync steps)?
Any specific configurations or solution packages that must be deployed in Dataverse for custom entities to appear in the Dual-Write table mapping list.
Security or permission prerequisites needed on either side (F&O or Dataverse) to view custom objects.
Known limitations or extra steps for custom objects to flow all the way through Synapse Link to ADLS/Power BI.
Additional Notes:
The Dual-Write core and extended solutions are installed.
The Dual-Write core and extended solutions are installed.
Standard entities are visible; only custom entities are missing.
My end goal is to achieve a working data pipeline F&O → Dataverse → ADLS → Synapse → Power BI.
If anyone has experienced similar issues or can outline the correct process, your guidance will be extremely helpful.
My end goal is to achieve a working data pipeline F&O → Dataverse → ADLS → Synapse → Power BI.
If anyone has experienced similar issues or can outline the correct process, your guidance will be extremely helpful.
Thank you in advance!
I have the same question (0)
All responses (
Answers (
694
