Unable to see contents of app in Production Environment

[deeteee]

Hello There,

I'm hoping someone on here could help me with this as I've been given the run-around with Microsoft for the past several weeks.

We've an app developed by another Team in PowerApps that is model-driven connected to a Dataverse backend, it simply displays relevant data in a tabular format which end users can report on. It was working fine in the Default environment but since moving it to a Production environment the app no longer loads.

This is how it looks in the default environment:

Meanwhile in the Production environment

Users are listed under production available users list

Running diagnostics against them is working fine

Users are a member of the Security role that was working fine under the default environment

Users are licensed with a Powerapps Plan 2 Trial license

We tried assigning a D365 test license and no effect

Does anyone know what causes the app to display like this? I can add the security role settings, I just didn't want this post to get too large

Thanks.

[AhmedSalih]

Hello, @deeteee, can you see the Main View Toolbar as in your development environment?

 

If my reply helped you, please give a 👍 , & if it solved your issue, please 👍 & Accept it as the Solution to help other community members find it more.

I am primarily available on weekdays from 6-10 PM CT and 5-10 PM CT on weekends.

Visit my Blog: www.powerplatformplace.com

[deeteee]

Hi @AhmedSalih no I cannot, all I see is a white screen where the main view toolbar should be.

The app works fine in the production instance when I am in the system admin role I forgot to mention.

[dpoggemann]

Hi @deeteee ,

Some questions to help clarify the situation...

1. Your production Dataverse environment has a solution you imported with all the tables etc.?  Are you able to go into the production environment in make.powerapps.com and view the records in the tables?
2. Is the model-app within the solution in production as well?  
3. I assume the users are assigned the appropriate security roles in the production environment?
4. Are you System Administrator role in the above screen shot for the production environment?

On the licensing side...

• The licensing you appear to have, Power Apps Plan 2 Trial, is not in the current licensing scheme for Microsoft.  The licenses should be Power Apps Per App, Power Apps Per User vs. the Plan 1 / Plan 2 types of licensing.  This should not affect the app as you show above though, they wouldn't be able to get in the application at all.

[deeteee]

Thanks @dpoggemann , to answer your questions:

1. Yes I'm able to see the records in the tables under my System Administrator role

2. Yes, it was exported from the default environment to the production environment, all looks fine when running the app under my account

3. Users are assigned to a custom security role for the app which gives them rights to the table, this was working in the default environment and was copied over to production, we've gone through all the settings and the permissions on both roles match. If we assign the System Admin role to an affected user then they can see the app fine.

4. Yes

If I'm reading it right, the license shouldn't impact the performance of the app? Even with the trial the end user should still be able to see it? We created the Production environment to get backups running but now if we have to license every user with a powerapps plan then it won't make the app very cost effective, extra costs like this I can see people scrapping the project.

Thanks for your help.

Regards, David.

[dpoggemann]

Hi @deeteee ,

I am not sure if it is the licensing that is stopping it from working, it definitely could be if Microsoft has started enforcing.  Overall you would need a paid Power Apps Per App or Power Apps Per User license to access Dataverse through a model-based app.

See the following on the Power Apps Plan 1 / Plan 2 as well:  https://learn.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#what-will-happen... 

[Fubar · Accepted solution]

Have you tried giving the users the out of the box "Basic User" security role in addition you your custom one?

[dpoggemann]

Good idea @Fubar ,

Might be some basic permissions missing in the setup of the custom role, this would be a good way to check this!

[deeteee]

Thanks @Fubar that was it! I was onto MS support earlier who suggested it, we got there after nearly a month 🙂

I knew it was something basic I was missing but had gotten mired in licensing, thanks also to @dpoggemann for his suggestions.