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,
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.
That menu item (Enable Entity Indexes for Synapse Link) does not appear anywhere in our F&O environments. Can you confirm if there's a specific release that it is available in?
- v-sgandrathi1 year agoCommunity Support
Hi Karen_Mendez2,
Thank you for your update and for reviewing your Finance and Operations (FnO) environment.
Please note that the “Enable Entity Indexes for Synapse Link” menu item is not available by default in all FnO versions. Its availability depends on several factors, including:
- The application/platform version of your FnO environment
- Whether Microsoft has enabled (flighted) the feature in your tenant
- Your user role or security permissions, as insufficient privileges may hide this option
To confirm, please check your FnO version under System Administration -- About and compare it to the Microsoft documentation for Azure Synapse Link compatibility.
Thank you.- BrianManchester11 months agoNew Member
v-sgandrathi I am running the most recent application/platform version for FnO and have searched the AOT. I do not see anything referring to Azure Synapse Link or Enable Entity Indexes. Where do I find this? How do you enable it? I'm working in a LCS/Tier2 environment and cannot seem to resolve this issue.
Thanks!
- v-sgandrathi11 months agoCommunity Support
Hi BrianManchester,
If you’re using the latest version of the FnO application or platform and don’t see the “Enable Entity Indexes for Synapse Link” option in AOT or menus, this is normal. The feature isn’t available directly in AOT. Instead, you can enable indexes for Synapse Link through a system administration workspace:
Go to System administration > Setup > Configure Azure Synapse Link, or, depending on your build, System administration > Setup > Azure Synapse Link > Enable Entity Indexes.
Here, you can run the “Enable entity indexes” batch job and choose to apply it to all entities or just those used in your Synapse Link. This will recreate the necessary system-maintained indexes for the FnO–Synapse synchronization.
If you still don’t see the menu, check that the Azure Synapse Link feature is enabled in Feature Management. Look for “Synapse Link for Dataverse” and make sure it’s activated.
After enabling the feature, check System administration again. The menu should now be available, allowing you to schedule the reindexing job.
For Tier2/LCS environments, remember to re-run this job after a database refresh, as refreshes can remove or disable these system-maintained indexes.
Thank you.