Third-Party Integration Receiving "Permissions Prevented the Action" Error on Fidesic Tables After BC Update

Symptom

A third-party integration (such as an AP automation connector, expense tool, or ERP middleware) begins failing with the following error after a Business Central update:

"Sorry, the current permissions prevented the action. (TableData 71669575 FDSIntegrationSetup Fidesic Integration Setup Read)"

Batches or transactions that were previously processing successfully now fail. The error typically appears in the integration's batch log or error report.

Root Cause

Business Central updates can reset or strip permission sets from service accounts and application identities. If a third-party integration connects to BC via a service account or an Entra Application identity, that account may lose its assigned Fidesic permission sets after the update, preventing it from reading the FDSIntegrationSetup table — which Fidesic requires as part of normal operation.

This is not a Fidesic bug. Fidesic is behaving correctly. The issue is that the integration's BC identity no longer has the required permissions.

Resolution

The Fidesic permission set needs to be re-assigned to whichever identity the integration is using to authenticate into BC. There are two places to check depending on how the integration was set up:

Option 1 — Entra Application (most common for modern integrations):

1. In BC, search for Entra and open Microsoft Entra Applications
2. Find the entry for your integration (e.g. InvoiceConnect, ExpenseConnect, etc.)
3. Scroll to the Security Roles section at the bottom
4. Add the permission set: FDSIDESIC ADMIN

Option 2 — Named BC Service Account:

1. In BC, go to Settings → Users
2. Look for a non-human user tied to the integration (check Authentication Email for service account addresses)
3. Open that user and assign the FDSIDESIC ADMIN permission set

Notes

• If you are unsure which identity the integration is using, contact the integration vendor's support team — they will know how their product authenticates into BC
• This issue can recur after future BC updates, so it is worth documenting which identity your integration uses and checking permissions as part of your post-update checklist
• If batches were succeeding before the update and failing after with this specific error, permissions are almost certainly the cause

Related Article: Sorry, the current permissions prevented the action - TableData 71669575 FDSIntegrationSetup