Announcements
No record found.
Hi cbaren12,
In Dynamics 365 Finance and Operations, using a data entity as a data source within another data entity—like trying to add DocuRefEntity—is not directly supported in the same way as adding tables. Data entities are designed to expose data externally and are not meant to be nested as data sources within other entities.
DocuRefEntity
Use the Underlying Table Instead Instead of adding DocuRefEntity, add the DocuRef table directly as a data source in your custom data entity. This gives you access to the document reference data and allows you to define relationships and mappings.
DocuRef
Define Relationships Manually Create a relation between your primary data source (e.g., SalesTable, VendTable, etc.) and DocuRef using the appropriate foreign key (e.g., RefRecId, RefTableId). This ensures the document references are correctly linked.
SalesTable
VendTable
RefRecId
RefTableId
Expose Fields via Staging or Extension If you need to expose DocuRefEntity fields specifically, you can:
Use Composite Entities (Advanced) For more complex scenarios, consider creating a composite entity that combines multiple entities or tables, though this requires careful design to maintain performance and data integrity.
Unfortunately, data entities cannot be used as direct data sources within other entities due to their abstraction layer. Working with the underlying tables is the best route.
Thanks and best regards, Daniele Note: This response was prepared with support from Copilot to ensure clarity and completeness.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 608
André Arnaud de Cal... 591 Super User 2026 Season 1
CP04-islander 430