You can manually import solutions using the steps in this article. You must import only those solutions that you've obtained from a trusted source. Customizations might include code that can send data to external sources.
- To import a solution that includes a plug-in assembly, the Create privilege on the Plug-In Assembly entity is required. By default, the System Administrator security role has this privilege, but the System Customizer security role doesn’t.
- When you import a managed solution, all component changes will be brought into the environment in a published state. However, when you import an unmanaged solution, the changes are imported in a draft state so you must publish them to make them active.
- To implement healthy application lifecycle management (ALM) in your organization, consider using a source control system to store and collaborate on your solutions, and automate the solution import process. More information: ALM basics in the Power Platform ALM guide.
When you import an unmanaged solution:
- You add all the components of that solution into your environment and can't delete the components by deleting the solution. Deleting the unmanaged solution deletes only the solution container.
- That contains components you have already customized, your customizations will be overwritten by the customizations in the imported unmanaged solution. You can’t undo this.
To import a solution:
Sign into Power Apps and select Solutions from the left navigation.
On the command bar, select Import.
On the Select Solution Package page, select Browse to locate the compressed (.zip or .cab) file that contains the solution you want to import.
Information about the solution is displayed. Select Import.
You may need to wait a few moments while the import completes. View the results and then select Close.
If you have imported any changes that require publishing, you must publish customizations before they are available.
If the import isn’t successful, you will see a report showing any errors or warnings that were captured. Select Download Log File to capture details about what caused the import to fail. The most common cause for an import to fail is that the solution did not contain some required components.
When you download the log file, you will find an XML file that you can open using Office Excel to view the contents.
You can’t edit an active routing rule set. Therefore, if you’re importing a solution that includes an active routing rule set into an environment where the rule already exists with the same ID, the import will fail. More information: Create rules to automatically route cases