Forum Discussion
FnO-812: Need to enable additional
- 1 year ago
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.
Hi Karen_Mendez2,
Thanks for the update and the screenshot.
If you don’t see the Enable Entity Indexes for Synapse Link option, it means the Azure Synapse Link integration feature hasn’t been deployed in your current Finance and Operations build. The FnO-812 error appears when required entity indexes are missing, and this feature is available only from App version 10.0.39 and Platform update 67 onward.
Check your version – Go to System administration > About and make sure it’s App 10.0.39 or higher.
Review installed packages in LCS – Confirm the Azure Synapse Link Integration package is listed.
If it’s not there, submit a support request from LCS to have Microsoft deploy or enable the module.
After it’s deployed, go to Feature management, enable Azure Synapse Link for Dataverse, and run System administration > Setup > Azure Synapse Link > Enable Entity Indexes.
Once enabled, rerun the Enable Entity Indexes batch job to resolve the error.
If the Azure Synapse Link for Dataverse feature still doesn’t appear after checking Feature Management and confirming you’re on the latest build, it’s likely that the Synapse Link integration components haven’t yet been deployed in your environment. This situation may occur if your LCS Tier-2 sandbox was refreshed from a backup or database that didn’t include the most recent extensions or features.
In this case, please open a Microsoft support ticket How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Mention that the Synapse Link integration feature (FnO-812 dependency) is missing even though you’re on the latest application/platform version.
The support team can validate if your environment deployment template includes the required model and enable it for you.
Thank you.
Hi BrianManchester,
Just looping back one last time to check if everything's good on your end. Let me know if you need any final support happy to assist if anything’s still open.
Thank you.
- BrianManchester10 months agoNew Member
v-sgandrathi No additional support needed at this time. Thanks for your assistance.