GitHub Actions Workflow Failure when trying to import a solution to the Power Platform - CanvasApp Import Error: MismatchingLogicalNames #1161
Unanswered
priyanka-agrawal2885
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team,
I am reaching out to seek help on a GitHub Actions workflow failure when we are trying to import a solution to the Power Platform. We have a set of workflows that first exports a solution from Power Platform from the dev environment and then imports it to the testing and production environment. We have configured them as reusable workflows since all the Power Platform solutions follow the same process. Strangely, the workflows are running successfully for all the other solutions except one.
The solution first gets exported from the Power Platform as an unmanaged solution using the following workflow:
Once the solution files are exported from the dev environment, we move it to the testing environment by importing it as an unmanaged solution back to the dev environment, exporting it as a managed solution, uploading to the artifact store and importing that artifact to the next environment i.e. testing. During this workflow, we are getting the following error when the same exported solution is being imported again to the dev environment:
I am providing the failing workflow below for your reference:
We tried checking the solution on the Power Platform to look for any name discrepancy, but we didn't find any. We tried troubleshooting this on our own for a long time but had no luck. We even reached out to the Power Platform support team long back, and they are still trying to find the issue. Our deployments are blocked for this particular app/solution due to this issue.
When the solution gets exported manually from the Power Platform, the exported files have no issue and the import of that manually exported solution is successful. Therefore, we feel it could be the issue with the PAC CLI being used within the actions we are using in our workflows. We are really looking forward to you guys for urgent support on this. Please let me know if you require any more details for further investigation.
Thanks and Regards,
Priyanka
Beta Was this translation helpful? Give feedback.
All reactions