@KOM_4410 @Powerhungry @gj84uw @PClancy_F242 @Mattbart Studio version 3.19075.25 has now been deployed to all regions. It contains a fix for the layout and rendering issues being reported. You will need save and re-publish your apps for the changes to take effect. Please remember it can take up to two minutes after publishing for the new version to become available for download. If any issues persist, please let us know! Thank-you for your patience.
@_Corey_ Not finding any change. Version changed and published under the new version, but the app still does not function correctly as it did prior to the new version push on Friday.
Session ID: 019a6b00-4f0e-4372-9d1a-f7bbdf66f03f
BTW it shows its published under 3.19075.25 but when i go to Session details it says PowerApps 3.19073.18. Why would this be??
Hi, I ended up fixing my original issue by re-creating the form again because I was in a hurry for release. Luckily that worked!
I hope this final fix had solved any future problem.
@Mattbart I don't see any errors in our telemetry for the session ID you provided. Are you able to provide a copy of your app for us to examine? You can save it to a shared folder (ex. OneDrive) and provide a link in a private message. We would just be examing the structure of your app to determine where the layout is failing. We would not be able to access any of your data.
As for the version number, when you view session details, it gives you the player version and not the published app version. The two have a slightly different deployment cadence. However, we probably should be showing both version numbers to avoid any confusion.
@_Corey_ Any update?? This has brought my business operations to a grinding hault. I get a call yesterday from MS support with vague update that the "internal team is working on a global issue" and then an email from them that i need to clear my "all cookies-cache and republish the app" which i did and served no purpose.....deseperate here!!
If the fix didn't fix your app, it might be possible that your changes from around the same time also impacted your app. You could try to reset to a previous version before the cascading dropdown change and see if that works. If it does, then you probably need to look at your formulas (I'd recommend either resetting to the most recent version again and trying to fix it or "save as" the cascading dropdown version and have both open side-by-side and carefully adding the cascading to the old version). And, if resetting doesn't fix it, then we have a stronger indication that it may be a (possibly separate) product issue.
Check it out!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand