microsoft
PA3015: Property Removed: AnalysisOptions.DataflowAnalysisFlagStateToggledByUser
Describe the bug
We are using the unpack solution action with the ProcessCanvasApp parameter set to true in our DevOps pipelines (v2). In one project, we have encountered an error when trying to run the pipeline after we have changed some buttons and toggles in the canvas app. If we set ProcessCanvasApp to false, the solution can be unpacked without an error.
To Reproduce
Steps to reproduce the behavior:
- Set ProcessCanvasApp to true in the step to unpack the solution
- Run the DevOps pipeline
This is the error thrown by our pipeline (redacted for privacy):
-- unpacking Canvas app ***_***_9b485...
Unpack from D:\a\1\s\Power Platform solutions\PRJ1047***\PRJ1047***_unmanaged\CanvasApps\***_***_9b485_DocumentUri.msapp --> D:\a\1\s\Power Platform solutions\PRJ1047***\PRJ1047***_unmanaged\CanvasApps\src\***_***_9b485
source format version: 0.24
Warning PA2001: Checksum mismatch. Checksum indicates that sources have been edited since they were unpacked. If this was intentional, ignore this warning.
Microsoft PowerPlatform CLI
Version: 1.26.5+g670cdf9
Online documentation: https://aka.ms/PowerPlatformCLI
Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions
Error: Error PA3015: Property Removed: AnalysisOptions.DataflowAnalysisEnabled
Error PA3015: Property Removed: AnalysisOptions.DataflowAnalysisFlagStateToggledByUser
Error PA3011: Roundtrip validation on unpack failed.
You have found a bug; this is not a specific bug, rather an indicator that some bug has been encountered.
Please open an issue and log the entirety of this error log at https://github.com/microsoft/PowerApps-Language-Tooling
We have exactly the same problem in our devops pipelines but only on certain PowerApps solutions. We are currently trying to upgrade ALM Accelerator to the latest version to see if it fix the issue
We successfully updated ALM Accelerator with no evolution of our pipeline problem.
We tried to restore an old version of the application that was putting our pipeline to error and it just worked...
We are currently looking for what in the powerapp could bug the powershell pac command (yes we executed it locally as well)
Yes, we experienced the same thing. It seems to be some change in the app that prevents the command from executing correctly, although the error message seems to point to something Dataflow-related.
From: h-marti @.> Sent: Tuesday, 12 September 2023 17:00 To: microsoft/PowerApps-Language-Tooling @.> Cc: Johannes Schinzel @.>; Author @.> Subject: Re: [microsoft/PowerApps-Language-Tooling] PA3015: Property Removed: AnalysisOptions.DataflowAnalysisFlagStateToggledByUser (Issue #493)
We successfully updated ALM Accelerator with no evolution of our pipeline problem.
We tried to restore an old version of the application that was putting our pipeline to error and it just worked...
We are currently looking for what in the powerapp could bug the powershell pac command (yes we executed it locally as well)
— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerApps-Language-Tooling/issues/493#issuecomment-1715895339, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATZMRVLBE2FONOGK7KZNN2LX2B2HVANCNFSM6AAAAAA4UVAJFQ. You are receiving this because you authored the thread.Message ID: @.***>
The problem seems to be with any newly published application/solution, either an existing one that is updated or a just created empty app.
The app manifest too seems to be different as multiple parameters have changed (see attached files) CanvasManifestUnstable.txt CanvasManifestStable.txt
We are only seeing this problem with one app so far. Other (canvas) apps we have changed later still run through the unpack step without any issues.
From: h-marti @.> Sent: Tuesday, 12 September 2023 17:32 To: microsoft/PowerApps-Language-Tooling @.> Cc: Johannes Schinzel @.>; Author @.> Subject: Re: [microsoft/PowerApps-Language-Tooling] PA3015: Property Removed: AnalysisOptions.DataflowAnalysisFlagStateToggledByUser (Issue #493)
The problem seems to be with any newly published application/solution, either an existing one that is updated or a just created empty app.
The app manifest too seems to be different as multiple parameters have changed (see attached files) CanvasManifestUnstable.txthttps://github.com/microsoft/PowerApps-Language-Tooling/files/12588223/CanvasManifestUnstable.txt CanvasManifestStable.txthttps://github.com/microsoft/PowerApps-Language-Tooling/files/12588224/CanvasManifestStable.txt
— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerApps-Language-Tooling/issues/493#issuecomment-1715952129, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATZMRVLZ3HCFX2NRGY3PLPDX2B55NANCNFSM6AAAAAA4UVAJFQ. You are receiving this because you authored the thread.Message ID: @.***>
I can confirm we are also experiencing this issue as well.
Appears PowerApps has gone through an updated. Upgraded PAC to v1.26.6 and problem still occurs.
Older apps still work until application is saved/published.
Also experiencing this issue. Error misleadingly looks like below in AzDO, until you dig further:
##[error]error: 1
##[error]failed:
Unpacking Solution...
Read-only files will be over-written or deleted.
Also experiencing this issue across multiple versions of the power apps cli.
I have temporarily resolved the error by removing any usage of --processCanvasApps (docs) when running pac solution sync....
This prevents canvas apps from being unpacked but allows the unpacking of the other solution components.
We are using the ALM Accelerator the pipeline does the same command. We successfully completed the pipeline on Mon 11th. Tried importing the same solution since Wednesday and getting this same error.
Confirming we are also experiencing the issue.
Any canvas application that has had a change and is then saved and published in a solution that is the target of the unpack solution action with ProcessCanvasApp = true will throw the error.
Also confirming that setting the ProcessCanvasApp = false or running a pipeline against a solution where no update has been made to the canvas app won't throw the error.
The workaround is to downgrade App version to 3.23084.14. https://github.com/microsoft/powerplatform-build-tools/issues/536
Confirmed we are also seeing exactly the same issue with Power Platform Github Actions. So it looks like a PAC CLI related issue rather than anything specific to do with Azure DevOps
Thanks for the discussion. We are looking into it.
Any updates or workarounds? This has stopped our entire development process and postponed a go-live for clients?
Thanks for the discussion. We are looking into it.
Any updates or workarounds? This has stopped our entire development process and postponed a go-live for clients?
Downgrade the app authoring version to 3.23084.14 and then recommit. This solved the issue for me.
Thanks for the discussion. We are looking into it.
Any updates or workarounds? This has stopped our entire development process and postponed a go-live for clients?
Downgrade the app authoring version to 3.23084.14 and then recommit. This solved the issue for me.
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/studio-versions
Will confirm suggested workaround provided by rfarris2000.
Provided link above for working instructions
Confirmed downgrading Authoring Version to 3.23084.14 works. Thank you @rfarris2000 and @gytisa
Is there any timeline for a permanent resolution? Rather not have our canvas apps pegged to an old version.
Hey all, sorry for the inconvenience here. This was a regression caused by some changes in studio which was ultimately fixed in August. A new version 1.27.x of Pac cli came out last week and it has the fix for this issue. I'd recommend to update your pac cli version to the latest and it should fix this for you.
Hi Everyone, I have tried to update to latest CLI and same issue. Anything progress from anyone? Thanks!!!
@vieira22 Please let us know what version you are on. We could take a look at it. Also it would be great if you can send your .msapp to our team (paadvmakers AT microsoft DOT com)
Seeing a similar error and can no longer try reverting to 3.23084.14. My errors are: Error: Error PA3015: Property Removed: TopParent.Children[0].Children[0].Rules[2].Category Error PA3015: Property Removed: TopParent.Children[0].Children[0].Rules[2].InvariantScript Error PA3015: Property Removed: TopParent.Children[0].Children[0].Rules[2].Property Error PA3015: Property Removed: TopParent.Children[0].Children[0].Rules[2].RuleProviderType
That repeats with increments in the references for the Children/Rules arrays.
Same on our end. We are using Power Platform Built Tools (not controlling the PAC version as far as I understand) and it happened right after we added some test suites/cases into our solution.
Downgrading below 3.2.24052.21 does not seem supported in the web UI.
Same on our end. We are using Power Platform Built Tools (not controlling the PAC version as far as I understand) and it happened right after we added some test suites/cases into our solution.
Downgrading below 3.2.24052.21 does not seem supported in the web UI.
Unpacking canvas apps tooling and format will likely change soon. Please check announcement and demos:
Power Apps is making it easier for developers to build with Microsoft Copilot and each other Enable every developer to collaborate with low code + pro code
Interesting announcements. Any idea about the rollout dates for the native Git integration?
Interesting announcements. Any idea about the rollout dates for the native Git integration?
As it was said during Build conference native Git integration is in private preview right now.