After recently enabling co-pilot functionality in our environment and seamlessly integrating it into our model-driven app, we found ourselves facing an unexpected roadblock. To our dismay, our solution imports suddenly encountered a perplexing failure. The error message that surfaced was a baffling one: “Import of app module(s) failed: Setting cannot be created or updated for non-overridable setting definition.“
In our quest to troubleshoot this issue, we engaged with support to unravel the intricacies of the problem. The detective work paid off, as we successfully identified the culprit – the app xml within our solution’s zip file held surplus feature flags that had unwittingly sneaked in, causing unintended disruption.
With Microsoft now in the thick of resolving this predicament, working towards an effective solution, we’ve managed to devise an interim workaround. Enter manual intervention: to regain control, we need to take matters into our own hands. Here’s the drill – first, we fetch the solution from its source. Next, we delicately extract and open the solution’s customization.xml file. With surgical precision, we surgically remove the undesired tags, eliminating the extra baggage.
<appsetting settingdefinitionid.uniquename="msdyn_enablecopilotemailassist">
<iscustomizable>1</iscustomizable>
<value>true</value>
</appsetting>
<appsetting settingdefinitionid.uniquename="msdyn_enablesalescopilotchat">
<iscustomizable>1</iscustomizable>
<value>true</value>
</appsetting> Having meticulously refined the customization.xml, we seal the solution back into its zip file and perform an import operation into the target environment. Voilà! The problem stands vanquished, thanks to this strategic maneuver.
As Microsoft continues their efforts to provide a comprehensive solution, this hands-on approach stands as the bridge to overcoming this unexpected hurdle.
My Trial 