Hi @CU12020826-0,
To answer the four questions:
1. Are there any features, configurations, or prerequisites that must be enabled for an F&O table to appear when creating a Link to Microsoft Fabric?
A] Pre-requisites for Synapse link for Fabric setup in D365 FO include:
- FO environment cloud hosted link to Power Platform (Dataverse)
environment.
- Power Platform admin role and D365 System admin role (preferably
during configuration).
- Allow Row version change tracking (DB Sync post enablement).
. - Fabric workspace with proper capacity and storage account in Azure to
host the tables.
2. Do the underlying F&O tables need to have specific properties enabled, such as change tracking or any other data-sharing configuration?
A]Link to Fabric relies on row version change tracking enabled for Synapse link for Fabric.
3. Are there any restrictions on which standard or custom F&O tables are supported?
A] For standard tables if row based change tracking is enabled then the custom tables work. Tables like DataArea, UserInfo, SecurityRoles are included automatically and will be updated every day. Unsupported tables include staging tables/temporary tables, custom tables without rowversion, deprecated tables with DEL_ prefix.
4. Is there a recommended way to verify why a specific F&O table is unavailable?
A] A F&O table not being available could be either because:
- Allow row version change tracking is not being enabled.
- Custom tables with no database synchronization or a model build is not
completed that leads to tables not being available or showing up on the
Dataverse side.
. - Large tables like LedgerJournalTrans,CustTrans,VendTrans, InventTrans take some time to refresh between D365 and Synapse link for Fabric so refresh times could be different.
References:
https://learn.microsoft.com/dynamics365/fin-ops-core/dev-itpro/data-entities/rowversion-change-track
https://learn.microsoft.com/power-apps/maker/data-platform/azure-synapse-link-select-fno-data
Hope this helps. Happy to answer questions, if any.