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

Corrupted Component

hakisan_1-1594863344244.png

 

Anyone else having this problem?
I just opened my app today and all the component are corrupted. Is this caused by a new update to Powerapps or is it just a common thing to happen? Appreciate some help because it's gonna be tedious to re-import and config the component again.

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @hakisan ,

According to the error message that you mentioned, it seems that this issue is related to CRM (maybe a update to PowerApps). Currently, I could not reproduce your issue on my side.

 

If you would like to get further help in this issue, please consider submit an assisted support ticket through the following link:
https://powerapps.microsoft.com/en-us/support/pro

 

In addition, you could consider use the following previous version of PowerApps to open your canvas app:

https://create.powerapps.com/v3.20064.23.155867258/studio/

then check if the issue is gone.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Apologies for the error. This actually was a regression issue which made it to production and certain canvas apps created during that time period will be affected. Apps would need to remove and re add the components to address this and it will not get automatically addressed by future updates. 

 

This is one off case and hit the preview PCF canvas feature, this does and should not happen with general app upgrades. 

Sorry again for the inconvenience.  Please reach out to me if there are any further questions. 

 

hemant 

View solution in original post

7 REPLIES 7
bcampbell13
Advocate II
Advocate II

I don't get that error message, but I started having one of my components corrupted about 7 hours ago.  I see the version of my app changed from: 3.20064.23 to 3.20065.16 about the same time the problem seem to start.

v-xida-msft
Community Support
Community Support

Hi @hakisan ,

According to the error message that you mentioned, it seems that this issue is related to CRM (maybe a update to PowerApps). Currently, I could not reproduce your issue on my side.

 

If you would like to get further help in this issue, please consider submit an assisted support ticket through the following link:
https://powerapps.microsoft.com/en-us/support/pro

 

In addition, you could consider use the following previous version of PowerApps to open your canvas app:

https://create.powerapps.com/v3.20064.23.155867258/studio/

then check if the issue is gone.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thank you for your reply. @bcampbell13  @v-xida-msft 
I have resolved the problem by using the previous Powerapps version that @v-xida-msft  provided.

I was able to resolve my problem by restoring from: 3.20065.16 to 3.20064.23.  

 

I believe the 3.20065 build has a bug or the upgrade was a problem. 

Apologies for the error. This actually was a regression issue which made it to production and certain canvas apps created during that time period will be affected. Apps would need to remove and re add the components to address this and it will not get automatically addressed by future updates. 

 

This is one off case and hit the preview PCF canvas feature, this does and should not happen with general app upgrades. 

Sorry again for the inconvenience.  Please reach out to me if there are any further questions. 

 

hemant 

@HemantG ,

 

I appreciate the update, but that doesn't quite line up to what we experienced.  We re-added the component many times, even re-made it from scratch and it didn't fix the issue.

 

The only that actually did resolve it, I see microsoft rolled back to version 3.20064.23.  Our application sudden started saving in the older version, so I assume that was Microsoft rolling it back.  In that version everything works fine, no code changes needed.  but in the new version, no matter what we did worked.  As mentioned, we removed the component, and re-made it with normal controls, so no component was even used and we still had the same problems.

 

I share this info if for some reason it helps others.

Apology for the error and confusion.

 

Did you try opening the app in 32007.1, removing all the component as prompted, then re-import and add the controls to the screens? Or did you try removing the controls, re-add them in 32006.5/32006.4, then opening them in 32007.1?

Are you running into this issue even when creating app from scratch in 32007.1?

Helpful resources

Announcements
October Events

Mark Your Calendars

So many events that are happening this month - don't miss out!

Ignite 2022

WHAT’S NEXT AT MICROSOFT IGNITE 2022

Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.

Power Apps Africa Challenge 2022

Power Apps Africa Challenge

Your chance to join an engaging competition of Power Platform enthusiasts.

Users online (3,719)