PRB: 'Zetadocs could not perform the Authorization' error when using Documents FactBox

This Zetadocs technical note applies to:

• Zetadocs - AP automation and bulk emailing extension
• Business Central 2025 release wave 1 (version 26)

Symptom

Some users may encounter the following error messages:

• "Zetadocs could not perform the authorization."

• "Zetadocs could not perform the authorization. No refresh token was supplied for user."

• "The changes to the Zetadocs Authorization Manager record cannot be saved because some information on the page is not up to date. Close the page, reopen it, and try again."

These errors can appear when accessing the Documents FactBox. Even after completing the sign-in process, users may still receive the same error or a variation of it.

Cause

The issue appears to be isolated to an update for Business Central 2025 release wave 1 and may be related to changes in how authentication tokens are handled in the backend of Business Central when interacting with third-party extensions such as Zetadocs.

Resolution

You can work around this issue by applying the following steps:

1. In the Business Central client, search for and open the 'Zetadocs Authorization Manager' page
2. Click the Zetadocs button, then the Sign Out button on the Action bar to clear the current user entry (or entries)
3. Click the Zetadocs button, then the Sign In button on the Action bar
4. A pop up will appear with the text "Zetadocs requires permission to access SharePoint Online to store and retrieve documents." Click Yes on this pop up
5. Follow the instructions to login to SharePoint in the browser window that launches
6. Once you have signed in and authorized on the browser, return to the Business Central browser tab and in the Zetadocs Authorization Manager, click the Zetadocs, Sign In button on the action bar a second time.
7. After this has been clicked make sure the Last Refresh column is populated

Once the steps are complete, the issue should be resolved for the impacted user.

If you continue to experience issues, please contact us at support@equisys.com

Status

Equisys is aware of this issue and will update this technical note when a longer-term solution is found.

Last updated: 1st October 2025 (MB/NT)