Hi,
I didn't changed a thing, and few of my screen layouts got completely destroyed, due to some update of Power Apps I suppose...
Width of screen disappeared, and the layout was compressed to some line. After rearranging the proper width, the layout is destroyed, as all other elements inside that screen also have width set to nothing.
This happened to multiple (6) of my screens that contain around 50 elements of each.
Please revert this, as I don't have time to deal with downloading package, changing JSON data and patching the package myself as shown here https://www.youtube.com/watch?v=-HLLF2ZRaXc.
My appID: 46ae0a46-0394-4f44-b444-7a1793755672
Solved! Go to Solution.
Here are some mitigation steps you can try until MS can post a solution.
Depending on when the user last saved their app, they may be able to use a previous version of the studio to fix their issue.
The app can now be opened in the latest version of the studio.
This guide assumes that the user has never used the ALM tool (PowerApps-Lanuage-Tooling). If they have, skip to step 5.
Screen1 as Screen: BackgroundImage: ='Background' Width: = Height: = Fill: = OnVisible: |- =UpdateContext({now: Now()});Screen1 as Screen: BackgroundImage: ='Background' Fill: = OnVisible: |- =UpdateContext({now: Now()});
I've seen several people report this, but it is far from everyone. I would suggest opening a support ticket to get it resolved for you.
I can confirm I'm having a similar issue. It may be be everyone, but I would guess many have not tried to editor there app today. Something was definitely done created a problem for some "unknown" set of users. Very frustrating.
I agree that its frustrating. But I've seen posts from a few users for about a week now. The point is that its not everyone so there is nothing we can really do for you here in the forums. Its something MS has to look at from the inside. To do that they need specific cases. That's why a support ticket is important.
I too have this happen to one of my PowerApps that I edit every day (getting ready to release but not used by others yet). This started for me either 4/3 or 4/4 or earlier and I just want on a screen that was affected. All of my screens use components and not all are affected - but almost half are. I also noticed I was seeing "Invalid operation divisible by zero" errors show up and they were cascading and incrementing higher when the app was open. I found the other thread with that error and changed my logic to include an if statement if the count of something in the denominator could possibly be zero. Even after these updates, it had no effect on the problem of the width.
I did some troubleshooting, but it all comes down to the fact that the component in a screen has a width and height of Zero. Even after changing the width or height to another value - when leaving the field it would revert to Zero. When looking at the components themselves in the components section, they have the proper height and width specified. I created a new screen and tried to insert a component and it. came in with Zero height and Zero width.
I created a new app, imported the components from the problem app and it only imported 6 of the 9 components. (no error - just left 3 of them out). I then exported the components from the problem app and imported to the test app and all came in. When adding a component to the screen it adds but lists "No Value" for the width and height despite the formula for both being app.designheight and app.designwidth. Changing the value for height and width to the real numerical value makes the component appear as expected.
The problem app and the test app are the only apps I have in this environment and the environment has the settings enabled to run the GeoSpatial Maps.
I have another powerapp in production in a separate (default) environment that also uses components but I have not edited so it doesn't appear to have any issues.
It's also ironic that @bcampbell13 is having issues as I think we possibly share the same name.
I will submit a support ticket to see if I get any traction.
MS is aware of the issue and support can suggest some workarounds for the immediate future. A fix has been identified and should roll out in the next week or two.
@Pstork1 ,
One to two weeks, that is really very painful. Microsoft has a reputation of their users being the testers, and I have to say with PowerApps, it really feels like this is the case.
This has happened several times. How do they expect companies to embrace this technology and rely on when they create outages like this. My dev team lost the entire day. Waiting two weeks is painful. Every time you touch a component, it resets them in the app, every occurrence of them. The component frame work is great in concept, but pretty less then great in reality.
Really disappointing from a company such as Microsoft.
Did you open a support ticket? I can forward the number to someone I know on the team to get it escalated.
Hi @Pstork1 @yes I did. The ticket number is
2104060040007229. Thanks for your help in this.
Hi @Pstork1 thank you for reply.
As Brian mentioned, if you try to set the width of screen to a proper function it does that, but then the components width is still 0, and while trying to set width and X-position on Properties tab from 0 to what it supposed to be (that information is saved inside Advanced Tab still) it goes back to 0, but after you choose different value it sets properly. But at the point where I have 4 screens not working with 20+ components setting all of this manually is no-go in terms of the time and deadlines.
I also raised a ticket to Microsoft about this.
Ticket number:
2104070050000542
Thank you for your patience
User | Count |
---|---|
261 | |
110 | |
97 | |
54 | |
39 |