If for any reason you have built a Canvas app outside of a Solution, and published it to multiple environments using the export/import functionality of Power Apps, if later you decide to add it to a solution (best practice) and redeploy the app to those environments using solution export/import, you will be duplicating the canvas app and the canvas app present in the solution will have a different ID and by consequence a different access URL, which can be a pain if there are a lot of users already using the app and you want them to use the new version (from the solution).
However, we can use a special Power Apps PowerShell cmdlet before importing the solution into those environments and avoid this hassle:
How to use the cmdlet and make the solution import work correctly keeping the same app ID
The following steps assume that app already is imported in multiple environments such as dev/UAT/Production and not added to any…
More About This Author
SharePoint and Office 365 Consultant/Developer always trying to get the best from Microsoft stack (Microsoft 365/Azure/Power Platform and related stuff).
Living in Ireland since 2018, I had previously worked in Brazil as a consultant/developer for Office 365, SharePoint and related technologies for almost 10 years.
- ModernWorkplace2022.07.16Moving a Canvas app into a solution and keeping the associated URL and ID in different environments
- ModernWorkplace2022.06.08Updating list views JSON formatters for a SharePoint list using Power Automate
- ModernWorkplace2022.05.19SharePoint lists custom View and Edit Buttons using JSON Formatting
- ModernWorkplace2022.05.14Power Apps: Patch data from the Office 365 Users connector to a SharePoint multi-user field without using collect