Import Solution failed - dependency msdyn_AppDeploymentMetadata

[TonyHoll100]

Hi, Import of Solution from Dev to Test environment is failing due to missing dependency msdyn_AppDeploymentMetadata.

The solution includes the AADUser table.

Would appreciate any suggestions. Thanks

[TonyHoll100]

The Solution also includes the USER table and this seems to cause the failure. I removed the USER table from the solution and it imported successfully. I created a new Solution with just the User table and it failed to import with the same failure message.

[parvezghumra · Accepted solution]

@TonyHoll100 Sounds like the User table has a dependency on msdyn_AppDeploymentMetadata. Does the error give you any more detail about what sort of component this is? Perhaps using the classic solution import experience?

If you can identify this actual component, then you can check in your source development environment, reviewing the solution layers on this component will tell you which managed solution this component originates from. And then you will be able to search into which package/app deploys this solution. More than likely your Test environment does not have this app/package version installed.

[TonyHoll100 · Accepted solution]

Hi Parvez, Thank you so much for taking the time to respond. Directly and indirectly you have solved my problem. So that the solution can be referenced by others I have marked this update as the Solution. Your help was invaluable.

Based on the advice from MS Support (see below)…

I removed the User table from Solution and re-imported to Test (which would remove User from Test solution)

I added only the components that had been changed in the User table (a View) into the Dev Solution and re-imported. (Previously I was including all components from the User table)

STILL did not update the View in Test.

Based on a similar problem on forum Solved: Re: Model driven app in managed solution is not up... - Power Platform Community (microsoft....

And your suggestion Parvez

 parvezghumra

Super User

‎07-06-2023 02:28 PM

@mattiabergo I would suggest trying to import/upgrade the solution using the classic experience, this will enable you to choose the option to "overwrite unmanaged customisations", as long as you confident that you don't have any unmanaged cutsomisation in your target environment that you wish to retain

I used the Classic experience with option to overwrite to import the solution and it updated the view successfully.

Helpful input from MS Support ..

... Regarding your initial issue, please let me explain, as you were facing an dependency to an Out-of-the-box internal solution msdyn_AppDeploymentMetaData, but you need only one column change in the User table, indicates for me and looks like, you have added the “User” table with all components and also out-of-the-box subcomponents included.

Please note, it’s not recommended, to add out-of-the-box tables with the option to “Include all subcomponents”/”Add all assets”. This can bring up additional, unwanted issues, as these Out-of-the-box tables usually already exist on every CRM environment and also your target environment. You should only put fields/components into a solution, which needs to be changed or a new created by you only.

More details about healthy ALM and this suggestions, you can find in our documentation:

• https://learn.microsoft.com/en-us/power-platform/alm/segmented-solutions-alm
• https://learn.microsoft.com/en-us/power-platform/alm/

[TonyHoll100]

Further clarification from MS support

some additional information about that behavior as well:

Usually, every time you modify any managed component, which was created by a managed solution, a so call “active” unmanaged solution layer is getting created on top for this component. This is the current behavior, which is reflected to the UI.

Once you are trying to simple update changes on your component, these changes are not getting reflected in UI, because it will only update the “lower” solution layer, instead of the existing unmanaged active solution layer on top for most of the regular components.

Therefore, the option for “Overwrite customizations” exist, because then the change will be also “copied” into your existing unmanaged solution layer.

There is no need to use the classic experience with the “Overwrite customizations” option and there is more recommended options: So to not run again in the future into the same issue, please check the solution layers of your view, and remove the “active” unmanaged solution layer. This will delete the unmanaged solution layer with the custom made changes, which you did in the past directly in this environment and will reflect the current changes of your solution. The next time you update this view with your solution, it should reflect the changes without the need for using “Overwrite customizations”.

More details about the solution layers and removing the unmanaged solution layers, you can find in our documentation at the following link:

• https://learn.microsoft.com/en-us/power-apps/maker/data-platform/solution-layers#remove-an-unmanaged...
• https://learn.microsoft.com/en-us/power-apps/maker/data-platform/solution-layers

[TonyHoll100]

Some more info from MS support....

One last this to add to my previous message:

At the beginning, you were telling you were facing an dependency issue related to the Microsoft Solution “msdyn_AppDeploymentMetaData”.

After talking with my Team I’ve got some more information and this indicates to us, that you have installed on your Dev environment the “Power Platform Pipelines” application addon. Please note, it’s not recommended, to install the “Power Platform Pipelines” D365 App to your Dev, Test or Production environment, in case you make usage of the PowerPlatform pipelines feature. This should be only installed on a dedicated HOST environment.

More about this, you can find in our documentation.

Therefore, it’s recommended, if you are not using the PowerPlatform Pipelines in your Dev environment, to uninstall these solutions, which were getting installed along with the “Power Platform Pipelines application”:

1)msdyn_AppDeploymentModelApp_managed

2) msdyn_AppDeploymentAnchor_managed

3)msdyn_AppDeploymentMetadata_managed

More details on this, you can find in our documentation at the following link:

• https://learn.microsoft.com/en-us/power-platform/alm/set-up-pipelines
• https://learn.microsoft.com/en-us/power-platform/alm/pipelines

[parvezghumra · Accepted solution]

Hi @TonyHoll100 ,

Thanks for following up and apologies for the delay in responding - I have been travelling.

Regarding the advice you have received from MS Support, I fully concur on the following issues:

1. Only including custom and customised managed components/subcomponents in your solutions and not entire tables with 'add all assets' option as a general recommended best practice. However, there are some cases where the platform brings in the full table int your solution sometimes with 'add all assets', without informing you, when it detects it as a dependency for the component you have added/modified.

2. The 'overwrite unmanaged customizations' option during the deployment of a managed solution should be used when you don't necessarily know exactly which components have unmanaged layers applied in the target environment, but you're sure that you want to overwrite them as part of the deployment. If you, however, are aware of the managed components in your target environment that are affected by an unmanaged layer preventing your managed components changes from taking effect, you can remove them more selectively as described by Microsoft support. But, again, there are certain scenarios, where the platform prevents you from removing unmanaged layers - I have seen this in the past, when attempting to do so, generated an error. But this may have been fixed recently.

3. I don't know much about Power Platform Pipelines to be honest, but I wasn't aware that it had to be installed into it's own dedicated host environment that is not the DEV, TEST or PROD environment

[TonyHoll100]

Thanks again Parvez, your input is very much appreciated.