Skip to content

Commit edd38a2

Browse files
authored
resolve the warning
1 parent b0864e6 commit edd38a2

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Missing dependencies during solution import in Power Apps
33
description: Works around an issue about missing dependencies that occurs when you import a solution in the target environment in Microsoft Power Apps.
44
ms.reviewer: matp
5-
ms.date: 03/13/2025
5+
ms.date: 03/14/2025
66
author: swatimadhukargit
77
ms.author: swatim
88
ms.custom: sap:Working with Solutions\Dependencies prevent a solution import
@@ -61,13 +61,13 @@ You can find these dependencies in the **Unmanaged components** section of the *
6161

6262
The following example illustrates a scenario when a system administrator performs a solution import and encounters a missing dependencies which has applications, managed solutions and unmanaged components missing.
6363

64-
:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-update-experience.png" alt-text="Example of the application upgrade link for a component with missing dependencies." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-update-experience.png":::
64+
:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-updated-experience.png" alt-text="Example of the application upgrade link for a component with missing dependencies." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-updated-experience.png":::
65+
66+
Here the solution has taken dependencies on the components of two applications which are missing in the target environment. One application is not installed, and the other application is installed but outdated in target environment.
6567

66-
Here the solution has taken dependencies on the components of two applications which are missing in the target environment. One application is not installed, and the other application is installed but outdated in target environment.
6768
The information for each application missing is provided in the format <solution_name> (<solution_version>) from <application_name>. When expanded further, component information is provided. Next to application name is Install or Update button to redirect the user to Power platform admin center for Install or Update.
6869

6970
The solution has also taken dependencies on the components of three managed solutions and two unmanaged components. Expanding each section will help to determine more details. These can be resolved based on the instruction provided above.
7071

71-
7272
> [!TIP]
7373
> 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

Comments
 (0)