You’re offline. This is a read only version of the page.
Hello All,
I am deploying managed solution from CRM 2013 Dev environment to CRM 2013 SIT environment.
During the import I am facing the below error:-
"The Form XML does not conform to the required schema. A schema validation error has been detected at line 0, position 0. Details: There is a duplicate key sequence 'Regarding_ID' for the 'UniqueName' key.
I have search for specific sequence "Regarding_ID" in Customization.xml and came to know that this is parameter defined in form properties of "Campaign Response" entity.
Does anybody have idea how to resolve this issue?
Regards
Manish Sharma
I've had the same issue today, so I'm going to just put my outcome here for prosterity.
My error was slightly different from Manish's error. Mine ended with:
A schema validation error has been detected at line 0, position 0. Details: The element 'events' has incomplete content. List of possible elements expected: 'event'.
I did have to get some support from my Microsoft Partner on this one, so can't take the credit. However, it was an issue where I had accidentally made a change to my test environment that was meant to be made in my Dev environment against the offending form (which was identified through the GUID that is supplied in the error).
Here are the steps I took to rectify it:
1. In the environment to which you are promoting (in my case, I was promoting from Dev to Test - so this was carried out in the Test environment), open the Customize the System in the Customization area in Settings
2. Find the offending Form in its parent entity (which will be highlighted in the error message).
3. Select the Form by ticking next to it.
4. Select the "More Actions" drop-down and select Solution Layers
5. In this screen, you should see where the layer has come into the base D365 configuration by being edited in the Managed entity (this is because I had allowed customizing of a managed entity)
6. There should be a button to the right of the Solution name with 3 dots (only there if it has been completed in this way, not if you last upgraded through importing a managed solution)
7. In the 3 dots is the option "Remove Active Customizations", select this.
8. There isn't much in the way of messages or timing. I had to close down the window and re-open to see that the solution layer had gone.
9. I went back and checked, it had rolled back to the previous form.
10. I could then apply the upgrade without an issue.
I hope this helps someone else out who may have made this same silly mistake, and is now sitting at 3:22 am trying in vein to get an upgrade through with Google as their only lifeline.
Hi Manish Sharma,
You only need to remove the duplicate 'Regarding_ID' key sequence from the customizations.xml file and not all 'Regarding_ID' key sequences. You will need to do this to import your solution into the target instance.
Hello Adrian,
Thanks for your response, but currently we have requirement to use these parameter in our custom page and I cannot remove those parameters from formxml.
Also I am this issue came while I am deploying the holding solution.
Regards
Manish Sharma
Hi Manish Sharma,
This is definitely an issue with the customizations.xml file. You will need to remove the duplicate 'Regarding_ID' key sequence from this file, zip your modified solution, and import it into the target instance.
Share
Report
All responses (
Answers (
57
