Forum Discussion
FnO-812: Need to enable additional
Hi Karen_Mendez2,
Thank you for using Microsoft Fabric Community Forum!Firstly:
The FnO-812 error means that the required indexes for Azure Synapse Link are not enabled in your Finance and Operations (FnO) environment. These indexes are essential for efficient and reliable data extraction from FnO tables to Synapse. This error usually happens if the necessary indexes for certain tables haven’t been created or enabled, or if changes like a database refresh or reset have removed or disabled them.
For the second one:
Yes, a recent database refresh or restore in the UAT environment can remove custom or system-generated indexes needed by Synapse Link. These actions may also reset configurations that had previously enabled those indexes, which is a common reason for the FnO-812 error after environment refreshes.
To fix the error, please follow these steps: Go to the Microsoft troubleshooting guide at:
Azure Synapse Link for Dataverse trouble shooting guide - Power Apps | Microsoft Learn
Next:Usually, this means running the "Enable Entity Indexes for Synapse Link" batch job in your Finance and Operations (FnO) environment. Go to System Administration > Setup > Azure Synapse Link > Enable Entity Indexes. Here, you can pick the tables or entities to re-index, or select all. After making your selection, run the job to recreate the necessary indexes. This will help restore the indexing structure for smooth data synchronization with Synapse.
After re-indexing, check your Azure Synapse Link configuration in the Power Platform Admin Center to confirm that the tables are syncing properly and the required indexes are in place.
Lastly:
To prevent the FnO-812 error during future environment refreshes, it is advisable to document and re-run the "Enable Entity Indexes" batch job immediately after each database refresh. Where possible, automating this step as part of your post-refresh process can further reduce risk. Including this activity as a standard item in your UAT or Development environment refresh documentation is also recommended. Additionally, keeping an up-to-date list of entities connected to Synapse will make it easier to re-index them after any data restoration, supporting ongoing stability in your Synapse Link integration.
I hope this helped! Feel free to ask any further questions
Thank you.
Hello,
thx for your reply and the steps. Sounds valid... besides:
I`ve checked now 6 different customers, from UAT/TEST to PROD in different tenants and languages in front end: There is not Setup > Azure Synapse Link integration/form/button in F&O.
Is that available in just a specific F&O version upwards?
Do you know the URL endpoint for the integration? There was a span of month, when the Export to Datalake was first introduced, where you couldn`t enter the integration without proper url because the form wasn`t integrated in front end.
Hi Karen_Mendez2,
Thank you for checking across various tenants and environments.
You are correct that, during the early release phases of Azure Synapse Link (formerly “Export to Data Lake”), the integration setup was not accessible through the UI, and could only be reached via a direct URL. This may still be the case in certain environments where the feature has not yet been fully enabled.
You can use the following direct URL pattern to access the Synapse Link Index Enablement screen:
https://<your-environment>.cloudax.dynamics.com/?mi=SysAzureSynapseLinkIndexEnablement
Please replace <your-environment> with your actual FnO base URL.
If the link does not work or you receive a permission error, the feature may not yet be available in your environment or may require a feature flag to be enabled by Microsoft. In this case, it is recommended to submit a support request so the Microsoft team can verify your tenant's eligibility and assist with enabling the integration.
Thank you.