Fabric Link Setup

Hi Nirav_Synapx​,

There is an important distinction between the two sections in your screenshot.

The first section labelled Dataverse is not specifically the Finance and Operations entities section.

Finance and Operations data entities can appear there, but only after they have been enabled as virtual tables in Dataverse and row-version change tracking has been enabled for them.

Microsoft documents this in the Finance and Operations data selection guidance.

Finance and Operations entities normally appear under the Dataverse tables section and typically use the mserp_ prefix.

The second section, D365 Finance & Operations, represents the underlying Finance and Operations application tables directly.

The difference is mainly the level of abstraction.

A Finance and Operations data entity is a business-oriented abstraction over one or more underlying tables. Microsoft describes data entities as a way of representing a business concept such as Customer, Vendor or Sales Order in a more consumable shape.

For example, a customer entity can combine data that physically lives across several normalized Finance and Operations tables.

Microsoft explains this in the data entities overview.

A Finance and Operations table is closer to the physical ERP data model itself.

So I would normally choose an entity when:

• the entity already represents the business concept you need
• you prefer a simpler, business-oriented structure
• you do not want to recreate several joins yourself
• the entity supports row-version change tracking
• I would choose the direct Finance and Operations tables when:
• I need fields that the entity does not expose
• I need more detailed/raw ERP data
• the required entity cannot be enabled for change tracking
• I am comfortable modelling the Finance and Operations table relationships myself

Microsoft specifically notes that not every Finance and Operations entity can be enabled for change tracking. In those cases, they recommend using the underlying tables that make up the entity where appropriate.

Also, the direct Finance and Operations tables are not automatically selected when the Fabric Link is created. Microsoft says they must be added separately through Manage tables.

One other thing I would check in your screenshot is why the D365 Finance & Operations section currently shows 0 of 0 selected.

If you expect direct F&O tables to be available there, I would verify that the Finance and Operations environment is correctly linked to the Power Platform environment and that your F&O application/platform build meets the current Fabric Link requirements.

So in short:

Dataverse section -> Dataverse tables, including eligible F&O entities exposed as virtual tables

D365 Finance & Operations section -> underlying F&O application tables

For analytics, I would not automatically choose one over the other. I would first decide whether you want the business-shaped entity or the lower-level physical F&O tables.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.