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:
Set-AdminPowerAppDesiredLogicalName
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…
Source link
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.
Array
- Modern Workplace24 July 2024Power Pages Table Permissions: Configure permissions to see records from child Accounts
- Modern Workplace15 July 2024Copy Dataverse contact phone numbers across different environments based on Contact e-mail address using Power Automate
- Modern Workplace1 June 2024Get the current logged Power Pages user Contact ID via JavaScript and use it to create records assigned to the current user
- Modern Workplace11 May 2024How to get the current Azure Devops iteration name for a project using Power Automate