Have you ever attempted to open a Model-Driven app, but have encountered issues with properly getting into the app before an error is displayed on screen? Chances are you’ve got a lucky error that doesn’t give you much information other than a session ID and timestamp so you can contact support! Contacting support could be one way to find out what’s going wrong, but if you’re anything like me you’ll prefer a much quicker way to find out what’s going wrong with your app so you can get it fixed pronto!
In this blog post, I’m going to show you a neat trick that lets you identify what could be going wrong with your Power Apps so you can quickly resolve the problem!
So, recently I encountered this problem myself when deploying the Centre of Excellence (CoE) Starter Kit to a production environment in my tenant. I followed all of the steps outlined by Microsoft including sharing the relevant data and apps with the correct security roles with users, however as a user who didn’t own the app, and who wasn’t someone with elevated privileges such as System Administrator in the environment, I wasn’t able to get into the Power Platform Admin View model-driven app that comes as part of the managed solution.
As you can see, I can’t get into my model-driven app, but I’m not getting an awful lot of detail as to what the problem is, making it difficult to resolve. But… there is a pretty simple trick to getting some more information about what is going wrong that will help me solve the problem here.
If you right click in your browser window and click on inspect you will see a pane appear on the right-hand side of your screen. Once you see this appear click ‘console’ in the top navigation bar.
Once you’ve opened the console you should hopefully see a number of yellow warnings and red errors.
These should hopefully explain a little further what the issue is and why your model-driven app won’t open!
In my case, I’m missing some permissions essential to opening a model-driven app. There are a number of tables users have to have permissions against to make any model-driven app work. These aren’t included in the security roles I’ve imported as part of the CoE Starter Kit solution.
So, I still need to add the ‘basic user’ security role at the least to easily fix this problem, or I’d need to create a custom security role and add the relevant tables permissions to make a model-driven app work. However, simply assigning teams or users the basic user security role would be a speedier option for me here.