O25DE2: A Little Gem I found - Visualizing Table Relationships Made Easy

 <for my reference only: O25 = October 2025; DE2 = with Data Entity Tag;>

While scrolling through LinkedIn, I stumbled upon something that made me happy and I think it will make your life easier too if you work with Dynamics 365 Finance & Operations.

We all know the data model in D365FO can feel like a maze sometimes. Tables, relationships, inheritance - it’s powerful, but not always easy to visualize. That’s why these two tools shared by a fellow community member may make it a bit more easy for us.

1. D365 F&O Table Relation Schema

https://daxonline.org/d365/entity-relation-schema.html
This tool generates a DBML schema for the area you select and lets you instantly visualize the data model. Perfect for:

  • Getting a clear overview of how tables connect.
  • Documenting your work for future reference.
  • Sharing diagrams with your team (you can render DBML using https://dbdiagram.io).

When I quickly tested it with CustTable and related tables like CustParameters, CustSettlement, and CustTrans, the output looked like below. Just for your info,

  • CustParameters is from AR module setup.
  • CustSettlement shows how transactions link during settlement.
  • CustTrans gives posted transaction details.

Seeing these relationships in a diagram instead of just SQL joins - might be helpful.  



2. D365 F&O Table Relation Finder

https://daxonline.org/d365/table-relation-finder.html
Ever wondered “How does this table connect to that one?” Use this tool to get answers for questions like that. It finds relationships between tables - even across inheritance and linking tables.

Example: I checked CustTable vs SalesOrderHeaderStaging and got 51 relationship paths! From direct links like InvoiceCustomer → CustTable to deeper chains involving Currency, InventLocation, and more. This first input might be helpful for you as a first step before you delve deeper.

Snapshot from my example attempt:



Why I’m Sharing This

Because a quick look at these tools made me think: “Wow, this could save few hours of digging through AOT or writing queries.” And if you’re documenting, troubleshooting, or just trying to understand the F&O data model better, maybe it is worth to give them a try.

There are other tools, which I haven't tried myself yet. But better get going - because not sure until when it will be possible to use them for free :) 

Comments

Post a Comment

Popular posts from this blog

D365FO - Copy of databases across environments

Image
When working with Dynamics 365 Finance and operations implementations, it is an obvious step to perform database movements across environments. We have been doing this in the previous version (AX2012) as well, where we had to change the environments related settings after the database copy manually. Now we D365FO , we might end up in different scenarios based on the Tier-level of the environment . So I have tried to identify the #4 major scenarios in here and share the approach I have used.  Copy of DB from Tier 1 env. to another Tier 1 env. Copy of DB from Tier 1 env. to a Tier 2 env. Copy of DB from Tier 2 env. to another Tier 2 env. Copy of DB from Tier 2 env. to a Tier 1 env. The below picture is an illustration of different types and corresponding solutions on a high level (sorry for my not-so-good-handwriting 😅) #1 Tier 1 -> Tier 1 DB copy:   This scenario can happen quite common if you have multiple tier-1 environment in your on-going project li...
Read more

Extended Data Types in Microsoft Dynamic Ax & EDT array

Image
·          An extended data type is extended from a base type or another extended data type. The difference is that an extended data type has a property sheet where information such as labels, length and left or right adjustment are stored. ·          EDT are a central part of MorphX. Whether you are adding fields to a table or declaring variables from X++, extended data types should always be used instead of using base types and the reason for that is Dynamics Ax provides powerful features to handle EDTs. ·          The best practice is to check before creating a new extended data type you should check whether in existing one will fulfill your needs. ·          If you have found an EDT which suits your needs, but another label or help text is required, you should create a new EDT with your requirements, but never mod...
Read more

Error: Field 'xxx' does not exist in D365Ops

Image
Today I encountered a weird error while working with newly created Enums and Tables in Visual Studio 2015 with a Dynamics 365 for Finance and Operations project. Error message while trying to build my project was: The underlying type 'BKA_Status ' or its base type for table 'BKA_GoalMaster' field 'GoalStatus' does not exist. The underlying type 'BKA_GoalTypes ' or its base type for table 'BKA_GoalMaster' field 'GoalType' does not exist.</Message> However, I had the 'BKA_Status' as well as 'BKA_GoalTypes' Enums already available in my project and even the project is Synchronized with the database. Root cause: To be honest, I was unable to find the root cause for sure. However, I imagine the error has something to do with the refresh of metadata because of the kind of solution which helped to resolve the error.  I have had 'Extends' property filled in with another Enum which was not existing in t...
Read more