microsoft / PowerApps-Tooling

Tooling support for PowerApps language and .msapp files
https://make.powerapps.com
MIT License
307 stars 103 forks source link

ALM error: Error PA3013: Property Value Changed: UsedTemplates[0].Name #667

Closed MarenBru closed 1 month ago

MarenBru commented 1 month ago

Describe the bug

I have the same issue with two different solutions. We are not able to find the error and need your help.

This error occours under "pac - Clone or Sync Solution":

Error PA3013: Property Value Changed: UsedTemplates[0].Name Error PA3013: Property Value Changed: UsedTemplates[0].Template Error PA3013: Property Value Changed: UsedTemplates[0].Version Error PA3013: Property Value Changed: UsedTemplates[1].Name Error PA3013: Property Value Changed: UsedTemplates[1].Template Error PA3013: Property Value Changed: UsedTemplates[1].Version Error PA3013: Property Value Changed: UsedTemplates[2].Name Error PA3013: Property Value Changed: UsedTemplates[2].Template Error PA3013: Property Value Changed: UsedTemplates[2].Version Error PA3013: Property Value Changed: UsedTemplates[3].Name Error PA3013: Property Value Changed: UsedTemplates[3].Template Error PA3013: Property Value Changed: UsedTemplates[3].Version Error PA3013: Property Value Changed: UsedTemplates[4].Name Error PA3013: Property Value Changed: UsedTemplates[4].Template Error PA3013: Property Value Changed: UsedTemplates[4].Version Error PA3013: Property Value Changed: UsedTemplates[5].Name Error PA3013: Property Value Changed: UsedTemplates[5].Template

.... and more all the way down to number 10.

This is the end message: Error PA3011: Roundtrip validation on unpack failed.

Used ALM Accelerator and this error is in DevOps.

Additional context

Using this version of the ALM Accelerator: 1.0.20240305.1

lasjoe commented 1 month ago

I have the same issue since today

Coding-Chem-Kitten commented 1 month ago

We have the same issue since yesterday.

pkm90 commented 1 month ago

Same issue

petrochuk commented 1 month ago

Do you have --processCanvasApps flag? Can you try removing it?

pkm90 commented 1 month ago

Do you have --processCanvasApps flag? Can you try removing it?

I'm having the issue when unpacking solutions locally. Removing the flag does remove the error, but it means that I can't store changes of canvas apps in version control.

Has there been a change from PowerApps side in terms of how canvas components are stored?

rfarris2000 commented 1 month ago

FYI - Rolling back the editor version to 3.24052.30 worked for us and allowed us to run the unpack command.

This error is different but is similar to this one #668. We were told they aren't going to fix it.

Coding-Chem-Kitten commented 1 month ago

Do you mean running a previous ALM version? Ours is an ALM issue.

rfarris2000 commented 1 month ago

No mean rolling back the Editor version in the canvas app:

image

MarenBru commented 1 month ago

We did try to remove a modern table component from the solution, which seemed to be solving the issue. However, one of the solutions is entirely dependent on that component, so we cannot remove it there. Is there another workaround?

MarenBru commented 1 month ago

Do you have --processCanvasApps flag? Can you try removing it?

Do you have an explanation or a link on how to do this?

tamilst2 commented 1 month ago

Same issue with pac canvas unpack with latest power apps version release. Combo box Microsoft_CoreControls_ComboBoxTemplate_dataField causing the issue (previous package pcfDataField_1.4.0). Once enabled to this new control, unable to revert back to older power apps version since it only show last 3 power apps authoring versions. So please provide a fix asap since unable to unpack canvas app (aware of this not to be used for production use but still a prob for development use).

lasjoe commented 1 month ago

As advised here: https://powerusers.microsoft.com/t5/Building-Power-Apps/Commit-to-GIT-error-since-today/td-p/2792452/page/2?lightbox-message-images-2794045=878423iAC3D0E6057F4B968

Adding &studio-version=v3.24052.30.298708436 to the end of app edit URL and saving the app temporarily fixes the issue.

Masciuniria commented 1 month ago

Thank you very much @lasjoe for sharing that. It worked!

Coding-Chem-Kitten commented 1 month ago

Thank you for sharing that @lasjoe it worked for us too!

marcelbf commented 1 month ago

it is same issue as 668