Forum Discussion
D365 FO Data Entity and Fabric
Hi MKBoopathy ,
Thanks for sharing the background and your specific requirements.
Based on what you described, the Link to Fabric feature actually aligns well with your goals. It allows you to virtualize D365 FO data entities directly into a Fabric lakehouse without physically copying the data.
Since your Power BI reports are already using those entities, this setup ensures continuity. It also avoids load on BYOD and supports integration with services like Logic Apps and Power Automate by exposing the tables through the lakehouse.
That said, if you still prefer to use the copy activity to bring the data into Fabric, the earlier steps still apply -
i. removing and re-adding the source in your pipeline typically refreshes metadata, and ii.regenerating the mappings in D365 FO ensures the newly added fields are exposed.
iii. For historical loads, segmenting by date ranges helps avoid failures and long runtimes.
Hope this helps. Please reach out for further assistance.
Thank you.
Community SupportHi MKBoopathy ,
Thanks for your question.
As suggested by jennratten , using the Link to Fabric feature is a more efficient option since it creates tables in the lakehouse without data duplication. This is particularly useful where near real-time data access is needed.
For more details, please follow this link: Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsoft Learn
However, if you still prefer to use the copy activity to ingest data into Fabric and you're not seeing the newly added fields from your extended Data Entity, try refreshing the metadata by removing and re-adding the source in your pipeline. In some cases, it might be also necessary to regenerate the mappings in D365 FO to reflect schema changes.
For loading large historical data, consider breaking the data load into smaller ranges, such as by year or quarter, instead of a full 4-year dataset in one go. This can help avoid pipeline timeouts and improve reliability.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi v-veshwara-msft,
We preferred to go with Entity in Fabric because,
1. Planned for future automations.
2. Integration with logic apps, power automation etc.
3. Currently we have only BYOD. The load on BYOD is high so we planned for Fabric.
Now as there Power BI reports are already connected with entity we are setting up the same in fabric. But we are facing some hard steps which I mentioned initially.
So need advices and suggestions.
- v-veshwara-msft
Hi MKBoopathy ,
Thanks for sharing the background and your specific requirements.
Based on what you described, the Link to Fabric feature actually aligns well with your goals. It allows you to virtualize D365 FO data entities directly into a Fabric lakehouse without physically copying the data.
Since your Power BI reports are already using those entities, this setup ensures continuity. It also avoids load on BYOD and supports integration with services like Logic Apps and Power Automate by exposing the tables through the lakehouse.
That said, if you still prefer to use the copy activity to bring the data into Fabric, the earlier steps still apply -
i. removing and re-adding the source in your pipeline typically refreshes metadata, and ii.regenerating the mappings in D365 FO ensures the newly added fields are exposed.
iii. For historical loads, segmenting by date ranges helps avoid failures and long runtimes.
Hope this helps. Please reach out for further assistance.
Thank you.
- v-veshwara-msft
Hi MKBoopathy ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.