O25DE3: Finding Table Names and Data Entities in D365 F&O

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

When working with data in Dynamics 365 Finance & Operations, one of the most useful skills is knowing where your data lives - which table or data entity holds the field you’re looking at. Why? Because this knowledge unlocks so many possibilities:

  • Extracting data for analysis.
  • Mass updates through Data Management.
  • Building integrations or troubleshooting issues.

Think of it as peeking behind the curtain to understand the architecture that powers your forms.

Why This Matters

Here’s a little reality check:

  • Different fields on the same form can belong to different tables.
  • A single field can appear in multiple data entities.
  • And not all users have equal access - System Admins have the most visibility (SysTableBrowser, entity lists, etc.).

So, if you’ve ever wondered “Where does this field actually come from?”, the below could guide you.

Part 1: How to Find the Table Name for a Form Field

  1. Open the Form
    Navigate to the form where the field lives. Say, CustTableListPage.

  2. Right-Click the Field
    Find the specific field, right-click, and Hover over Form Information. 
    Click on the follow up menu which opens up. 


  3. Check Control Information
    A dialog opens on the right. Under the Administration tab, look for:

    • DataSource → This is usually (but not always) the table name.
    • If unsure, verify using SysTableBrowser.
      https://<your_enviornment_name>.sandbox.operations.dynamics.com/?cmp=usrt&mi=SysTableBrowser&TableName=CustTable

  4. If DataSource Isn’t the Table
    Sometimes the field comes from a query or joined table. In that case:

    • Look at the Query statement in the dialog for hints.
    • Use SysTableBrowser to confirm.

Bonus Info 

Under Form Information, you’ll also see:

  • Form Name → Great for troubleshooting or customization.
  • Menu Item Name & Type → Super helpful for security design (Display, Action, Output).

Part 2: How to Find the Data Entity

  1. Open the Form
    Navigate to the form.

  2. Select “Open in Microsoft Office”
    Top-right corner of the form → click Open in Excel.

  3. Review Available Entities
    The list shows entities tied to this form.

    • A field may appear in more than one entity, so check carefully.

  4. Validate in Data Management
    Open the entity in Excel or Data Management workspace to see available fields.

Using the Data

Once you know the table or entity:

  • Build pivot tables, Power Query, or ad hoc reports.
  • Join tables on common keys for deeper insights.
  • Use entities for integration, data migration and reporting scenarios.

Whether you’re solving a mystery, building a report, or just curious - every table and entity you explore helps you understand the data architecture of D365 F&O a little better.

Why I Love This

Honestly, this is one of those small skills that makes a big difference. It’s empowering to know what’s behind the forms we use every day. And yes, sometimes it takes a little detective work - but that’s part of the fun!

<Inspired from: https://www.d365withbrittany.com/blog/data-entity-table-mapping-for-d365-fo-form-fiel>

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