While working on a Dynamics 365 project, I faced a strange issue that looked serious at first, but in reality did not block any functionality. Still, it was confusing for users and needed to be fixed. In this post, I’ll explain what happened, why it happened, and how I resolved it.
The Issue
Some users reported that when they tried to switch apps within Dynamics 365, an error popup appeared on the screen.
An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support.
Important points:
- The error appeared during app switching
- The app still loaded successfully
- Users were able to continue their work
- No functionality was broken
So technically nothing failed, but the popup confused users.
Why This Was a Problem
Even though users could continue working, the error message:
- Created confusion
- Made users think something was wrong
- Generated unnecessary support questions
From a project and user experience point of view, this was not something to ignore.
Initial Checks
I started with basic troubleshooting:
- Browser console logs
- Network tab
- Plugin trace logs
Nothing useful showed up. No clear error, no table name, no hint. That’s when it became clear this was most likely a security-related issue.
Observing the Pattern
After testing with different users, one pattern was clear:
- Users with custom security roles saw the error
- System Administrators did not
This confirmed that the issue was related to security roles.
Root Cause: Missing Privilege in Custom Security Role
After reviewing the custom security role, I found the issue.
One of the tables required by the app did not have Read permission for that role.
Even though:
- The table was not directly used by the user
- The app still opened
Dynamics 365 checks access to required tables during app loading. If any required privilege is missing, it may show a generic error popup.
This missing privilege was not captured in the browser console, which made debugging harder.
How I Fixed It
Once the cause was clear, the fix was simple.
- Go to Settings → Security → Security Roles
- Open your custom security role
- Search for the Role table (Display Name: Security Role)
- Provide Read permission at Global level
- Save and publish the security role
- Ask the user to refresh the browser and switch the app again
After this change, the error popup stopped appearing.
Tips to Avoid This Issue
- Always test apps using real business user roles
- Review security roles when new apps or components are added
- If no console error appears, check security roles first
- Compare working and non-working roles to spot missing privileges
- Do not ignore error popups even if functionality works
Related Reading
If you want to understand how apps and permissions work in Power Platform, you can also read this:
👉
Get started with Microsoft Canvas App
👉
How to Get and Set Field Values in Dynamics 365 CRM using JavaScript
No comments:
Post a Comment