Forum Discussion
Missing Dynamics 365 F&O tables when creating a Link to Microsoft Fabric
Hi Community,
We are creating a Link to Microsoft Fabric from our Dataverse environment.
While selecting tables for the link, we can see all the required tables under the Dataverse section. However, under the Dynamics 365 Finance and Operations (F&O) section, I see lot of tables, but required F&O tables are not available for selection when i search for it.
Could you please clarify the following?
- 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?
- Do the underlying F&O tables need to have specific properties enabled, such as change tracking or any other data-sharing configuration?
- Are there any restrictions on which standard or custom F&O tables are supported?
- Is there a recommended way to verify why a specific F&O table is unavailable?
The required tables exist in the F&O environment, but they are not listed in the F&O table-selection section while configuring the Fabric link.
Any guidance on the required configuration or troubleshooting steps would be appreciated.
Thanks.
Hi BharathKumarS,
There are a few eligibility rules here, and one distinction that may help is whether the object you are searching for is an actual F&O table or an F&O data entity.
For tables listed under the Dynamics 365 Finance and Operations section, you don't need to expose each one as a Dataverse virtual table or enable Dataverse Track changes individually. However, the underlying F&O table does need to support row version change tracking. Microsoft notes in the F&O Synapse/Fabric Link guidance that older application versions might not have every standard table enabled, while custom tables need row version change tracking enabled.
For a custom table, I would check that Allow Row Version Change Tracking is set to Yes. The underlying configuration is described in Microsoft's row version change tracking documentation. In a cloud-hosted environment, a database sync is also required after changing the table metadata.
Also note that staging, temporary and deprecated del_ tables aren't supported.
If the name you're searching for is actually an F&O data entity, that is slightly different. The entity needs to be enabled as a virtual table and support row version change tracking, after which it appears under the Dataverse section, normally with the mserp_ prefix.
I would therefore check the exact AOT table/entity name, the F&O application version, and the row version change tracking property first. If you can share one or two of the missing table names, it should be possible to narrow down which of these applies.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
3 Replies
Thankyou ShivekMaharaj ShahRukhSameer for Addressing the issue.
Hi BharathKumarS ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
Hi BharathKumarS ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
Hi BharathKumarS,
There are a few eligibility rules here, and one distinction that may help is whether the object you are searching for is an actual F&O table or an F&O data entity.
For tables listed under the Dynamics 365 Finance and Operations section, you don't need to expose each one as a Dataverse virtual table or enable Dataverse Track changes individually. However, the underlying F&O table does need to support row version change tracking. Microsoft notes in the F&O Synapse/Fabric Link guidance that older application versions might not have every standard table enabled, while custom tables need row version change tracking enabled.
For a custom table, I would check that Allow Row Version Change Tracking is set to Yes. The underlying configuration is described in Microsoft's row version change tracking documentation. In a cloud-hosted environment, a database sync is also required after changing the table metadata.
Also note that staging, temporary and deprecated del_ tables aren't supported.
If the name you're searching for is actually an F&O data entity, that is slightly different. The entity needs to be enabled as a virtual table and support row version change tracking, after which it appears under the Dataverse section, normally with the mserp_ prefix.
I would therefore check the exact AOT table/entity name, the F&O application version, and the row version change tracking property first. If you can share one or two of the missing table names, it should be possible to narrow down which of these applies.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
