Deploying Model-Driven App Solution: Duplicate AppSetting Component

(2) Share

Report

Posted on by mackenziestack

Hello Community,

I'm currently facing an issue while trying to deploy a model-driven app solution in my [Power Apps/Dynamics 365] environment. During the import process, I receive an error indicating that there are duplicate components within the solution. Below are the detailed error messages and the steps I've taken so far to troubleshoot the problem.

Error Details:

Failure Message:

Import of app module(s) failed: Invalid solution identified. There are more than one component with the same id added to the solution.

Component Name: AppSetting, Key: settingdefinitionid:b83c718b-dfdd-48b8-9091-b09fd31544e8

parentappmoduleid:00000000-0000-0000-0000-000000000000.

Exception Type:

System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]

Summarized Error Trace:

The import fails because multiple AppSetting components share the same settingdefinitionid.
The parentappmoduleid is set to 00000000-0000-0000-0000-000000000000, indicating a default or unassigned parent module.
Error Code: -2147155677

Context:

Environment: Development sandbox

Solution Type: Unmanaged

Deployment method: pipeline

I exported the solution and examined the customizations.xml file for duplicate app settings. I discovered that the msdyn_IsTeamsDynamicsIntegrationEnabled setting appears twice, which I believe is causing the issue. However, I'm unsure how to proceed from here. Should I edit the XML file directly, or is there an easier or alternative method to resolve this duplication?

Any assistance or guidance on resolving this deployment issue would be greatly appreciated. Thank you in advance!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

AA-24011952-0 7 on at

Like (3)

Report
Copy link

Link copied!

Hello, I experienced this issue as well, and from what I could tell the source of the issue is that our source Environment contained the Solutions "Customer Service Hub" and "Customer Service Workspace" which each have an AppSetting by this exact schema name.

The issue arises when one of the Settings gets customized, creating a cascade with its twin, and the App Modules themselves are not included in the unmanaged Solution, so the customizations.xml file dumps them under a catch-all "AppSettings" node that doesn't reference their respective unique source App Modules/base Solutions and a duplicate error arises.

The two options we faced were:

1) Add all of the originating App Modules to the unmanaged Solution so that they can be distinguished via the customizations.xml vs just the duplicated names.

2) Remove all customizations from Customer Service Hub (we went with this since we didn't actually need it), and the standalone appsetting nodes in cusotmizations.xml just disappear.

This does seem like a frustrating workaround for a Microsoft bug, however, and I'm curious to see their reply.

Hope this helps,

-Adam

3 people found this reply helpful.

Was this reply helpful? Yes No
Admin.Nick2 29 on at

Like (0)

Report
Copy link

Link copied!
I have the same theory as @AA-24011952-0. My only solution so far was to remove the extra setting with powershell in my pipeline.

$path = "$(UnpackedSolutionFolder)$(SolutionName)/src/Other/Customizations.xml" [xml]$doc = Get-Content $path do { $doc.ImportExportXml.appsettings.RemoveChild($doc.SelectNodes('//ImportExportXml/appsettings/appsetting[@settingdefinitionid.uniquename="appcopilotenabled"]').Item(0)) } while($doc.SelectNodes('//ImportExportXml/appsettings/appsetting[@settingdefinitionid.uniquename="appcopilotenabled"]').Count -ne 0) $doc.Save($path)

Was this reply helpful? Yes No
Suggested answer

11manish 845 on at

Like (0)

Report
Copy link

Link copied!
The error is caused by duplicate AppSetting entries (same settingdefinitionid) in your solution

Best fix is to clean duplicates in source environment (remove/re-add app or setting) and re-export

Manual XML editing should be last resort only

Was this reply helpful? Yes No
Ram Prakash Duraisamy 5,714 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @mackenziestack

Please find the below steps, download solution, Extract the solution and open Customization.xml and search for msdyn_IsTeamsDynamicsIntegrationEnabled and replace it one and Save the file and import in Source and destination.

Please mark as answer if my suggestion helps.
Subscribe here for More Useful videos : https://www.youtube.com/@rampprakash3991

Was this reply helpful? Yes No