You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md
+13-16Lines changed: 13 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,32 +31,29 @@ To work around this issue, follow these steps:
31
31
32
32
1. Select the **Show dependencies** button to navigate to the **Missing dependencies** page.
33
33
34
-
The **Missing dependencies** page lists all the components that are missing from the target environment. It also shows the solution or application from which the component dependencies are obtained.
34
+
The **Missing dependencies** page lists all the components that are missing from the target environment. It also shows three categories of dependencies from which the component dependencies are obtained. The component missing can be due to missing application, missing managed solution or missing unmanaged component.
35
35
36
36
2. Resolve this issue based on the different types of dependencies described in the following sections:
37
37
38
38
### Missing dependencies coming from a Dynamics 365 application
39
39
40
-
You can find these dependencies in the **Managed Solution** tab of the **Missing dependencies** page. To resolve this issue:
41
-
42
-
- If the application isn't installed in the target environment, [install the application](/power-platform/admin/manage-apps#install-an-app) from the Power Platform admin center.
43
-
- If the application is installed but has an outdated version, a link is provided next to the solution. This link will redirect you to the Power Platform admin center update page for the environment where you can update the application to resolve the issue.
44
-
45
-
The following screenshot shows the link provided on the **Missing dependencies** page.
46
-
47
-
:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependency.png" alt-text="Example of the application upgrade link for a component with missing dependencies." lightbox="media/missing-dependency-on-solution-import/missing-dependency.png":::
48
-
49
-
Select the link to open the upgrade application page in the Power Platform admin center.
50
-
51
-
:::image type="content" source="media/missing-dependency-on-solution-import/application-update.png" alt-text="Example of the upgrade application page in the Power Platform admin center." lightbox="media/missing-dependency-on-solution-import/application-update.png":::
40
+
You can find these dependencies in the **Applications** section of the **Missing dependencies** page. To resolve this issue:
52
41
42
+
- If the application isn't installed in the target environment
43
+
- System administrator will see an **Install** button, clicking the button will redirect to application install [install the application](/power-platform/admin/manage-apps#install-an-app) page in the Power Platform admin center. Choose the application and install it.
44
+
- Non system administrator will see a **Copy Install Link**. Copy the application install link and request your system administrator to install the application. Alternatively, system administrator can directly go to the [install application](/power-platform/admin/manage-apps#install-an-app) page in Power platform admin center.
45
+
46
+
- If the application is installed but has an outdated version in the target environment
47
+
- System administrator will see an **Update** button, click the button to open the application update page in Power platform admin center.
48
+
- Non system administrator will see a **Copy Update Link**. Copy the application update link and request your system administrator to update the application.
49
+
53
50
### Missing dependencies coming from another managed solution
54
51
55
-
You can find these dependencies in the **Managed Solution**tab of the **Missing dependencies** page. To resolve this issue, import the same version of the solution that's installed in the source environment into the target environment.
52
+
You can find these dependencies in the **Managed Solution**section of the **Missing dependencies** page. To resolve this issue, import the same version of the solution that's installed in the source environment into the target environment.
56
53
57
54
### Missing dependencies on the "Active" solutions
58
55
59
-
You can find these dependencies in the **Objects**tab. This indicates that the dependency is from unmanaged customization in the source environment. To resolve this issue, return to the source environment, include the missing components, export the solution again, and then import it into the target environment.
56
+
You can find these dependencies in the **Unmanaged components**section of the **Missing dependencies** page. This indicates that the dependency is from unmanaged customization in the source environment. To resolve this issue, return to the source environment, include the missing components, export the solution again, and then import it into the target environment.
60
57
61
58
> [!TIP]
62
-
> Another method to find dependencies of components is to open the solution file, unzip it, and then open the *solution.xml* file. In the *solution.xml* file, look for a `<MissingDependencies>` element. All the missing dependencies are listed within this node.
59
+
> Another method to find dependencies of components is to open the solution file, unzip it, and then open the *solution.xml* file. In the *solution.xml* file, look for a `<MissingDependencies>` element. All the dependencies are listed within this node.
0 commit comments