web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

BC 21 Update causes error "You do not have permissions to run this wizard"

(0) ShareShare
ReportReport
Posted on by 25

Hello,

We just updated a customer sandbox to BC version 21 which caused an API page to suddenly return error "You do not have permissions to run this wizard":

pastedimage1666857498312v2.png


There are 2 extensions in play here, A and B, where A has a dependency to B.
The API page is located in A, and has a standard table, Item, as SourceTable.

Functionality:
In the OnAfterGetRecord trigger of the API page we calculate a field value with help from a procedure in a wizard page (PageType = NavigatePage) in A.
This wizard page has a SourceTable in B and its procedure uses a non-local procedure defined in another table in B, to do this calculation.

The Oauth user described in Azure Active Directory is assigned the permissionsets of both A and B.
Both permissionsets includes the objects that are used in the calculation.

We tried having permissionset of A include the objects of B, to try to make sure the Oauth user had access to them, with no luck.

The only thing we tried that worked was to remove the usage of the procedure in B to do the calculation, but this is no permanent solution.


Have anyone else experienced this issue?
Is there any new permissions that has to be set with the BC 21 version?
Or is there any flaws to the logic I described?

Any help is much appreciated!


Best regards
Simen Fallaas

I have the same question (0)
  • Suggested answer
    DAnny3211 Profile Picture
    11,397 on at

    hello

    what permissions you have assigned on the Azure Active Directory Applications.

    can you send a screen

    DAniele

  • Verified answer
    fallaas Profile Picture
    25 on at

    Hello Daniele,

    We found the issue.

    The error was caused by having a permission check in the OnInit() trigger of the wizard page, which was triggered even when calling a procedure in the page.

    The solution was simply to move the permission check to OnOpenPage() in our case.

    Thank you :)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,010

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,270 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,085 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans