I understand that the property-set must have a unique name, but I thought it should be unique inside a data-set.
Unfortunately, I could work inside the test-harness and build the solution, but I couldn't import the solution after that. The error was about duplicate key
Import Solution Failed: CustomControl with name failed to import with error: The import manifest file is invalid. XSD validation failed with the following error: 'The import manifest file is invalid. XSD validation failed with the following error: 'There is a duplicate key sequence 'name' for the 'uniqueProperty' key or unique identity constraint.'."'."
and after renaming one of the property-sets it worked.
Is it a bug in the schema right now, or it's really designed to work only this way?
Kind regards, Diana ---------- Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."