cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Geoff_Olives
Advocate I
Advocate I

Dataverse Teams Power App runs fine in design mode but not when published

My Power App works fine in development and preview mode. I can either hold [ALT] or preview the app. Navigation works fine. lists populate with data. Icons look good.

I notice problems right away when I publish and run the application. I am using the default form. I have duplicated that form three more times in my app.

  1. I have a logo image file on the main screen in design mode. No icon shows when running the app from the published tab.

  2. Each screen can open but the icons on the top are missing or are rotated at very odd angles.

  3. My list of items on the left shows no entries. There is a scroll bar, but just moves through an empty list. I thought I could click in the white space and something would select, but nothing changes in the record panel on the right.

2020-11-19 10_22_36-New Message - Power Platform Community.png

I have published, saved, published again. Nothing changes the behavior. I can use Teams on different computers and get exactly the same results.

1 ACCEPTED SOLUTION

Accepted Solutions
Geoff_Olives
Advocate I
Advocate I

The app in the other environment is Dataverse for Teams. 

 

After waiting days and working on other projects I published one more time. I made no changes to my app. Now everything is working as expected. Maybe there is a lock placed on the deployed app and I had to wait for a timeout.

I do notice that when I'm going back and forth between Power Apps, Power Automate flows, and the environment I have to do that in a single windows in Teams. Which means I have to leave the designer and switch. If I were in a web browser I would just open up another tab and not lose the designer window. Sometimes when I switch between the app designer / out / back in, it says something about "another instance has this open" and asks me to stop that other instance.  I'll get the exact verbiage when I see the message again. 

View solution in original post

5 REPLIES 5
Geoff_Olives
Advocate I
Advocate I

I created a simple Power App in a different tenant and do not experience the errors above. My new Power App works great there. So either something is wrong with the app, or something is wrong in the tenant.

@Geoff_Olives have you tried creating another app in the same tenant in which you are getting the above mentioned errors? I haven't seen these so really curious as to what might be the reason. 

 

---
If you like this reply, please give kudos (Thumbs Up). And if this solves your problem, please mark this reply as a solution by selecting Accept as Solution. This makes it easier for others to find answers to similar questions. 

 

Thanks!

Hardit Bhatia

Microsoft Business Applications MVP

Microsoft Certified Trainer MCT

Blog | Twitter | LinkedIn | Facebook | YouTube  |  Email

I created an app in a different tenant without any trouble. This is the second app I created in this tenant. I'll try to create a new one. It is really unfortunate, since I can't find any way to export/import apps and this one was working and close to done.

 

Dataverse for Teams seems very interesting, but if the environment is limited and can't export/import my work then from a sustainability standpoint it isn't worth my time.

Hi @Geoff_Olives,

In the other tenant where it worked, was it Dataverse for Teams environment or standard Dataverse?

Unfortunately Dataverse solutions are supported yet in Dataverse for Teams to export/import apps. You can try to move environment by opening a support ticket: Dataverse: https://docs.microsoft.com/en-us/power-platform/admin/move-environment-tenant 

But before I would try just a simple dummy app in the problematic tenant to isolate app or environment issues. Are you also a global admin in that environment? If not, perhaps try to contact your system administrator to see if they enabled some kind of policies, proxies or firewalls that may cause the problem... Additionally you can contact Microsoft Support to get more details on the errors: https://admin.powerplatform.microsoft.com/support 

Good luck!

Geoff_Olives
Advocate I
Advocate I

The app in the other environment is Dataverse for Teams. 

 

After waiting days and working on other projects I published one more time. I made no changes to my app. Now everything is working as expected. Maybe there is a lock placed on the deployed app and I had to wait for a timeout.

I do notice that when I'm going back and forth between Power Apps, Power Automate flows, and the environment I have to do that in a single windows in Teams. Which means I have to leave the designer and switch. If I were in a web browser I would just open up another tab and not lose the designer window. Sometimes when I switch between the app designer / out / back in, it says something about "another instance has this open" and asks me to stop that other instance.  I'll get the exact verbiage when I see the message again. 

Helpful resources

Announcements
Power Apps News & Annoucements carousel

Power Apps News & Announcements

Keep up to date with current events and community announcements in the Power Apps community.

Power Apps Community Blog Carousel

Power Apps Community Blog

Check out the latest Community Blog from the community!

Users online (5,099)