The Problem is this, we’ve created a schema at a high level (020) in the blueprint called “link.” We’ve also created a category called “URI Classification” in the same publication, but have not defined any keywords. We’ve then used the category for a mandatory field in the link schema, but there are no default values available since we haven’t created any keywords.
Next, in a lower publication (040 Brand-Specific Content) we’ve created keywords for the category “URI Classification.” By default, when you create a new component of type “link” the product (Tridion) automatically chooses the first value in the category as if it were a default value for that field. However, it is not until you actually change the field value to something other than the first value (seemingly the default value to any normal person) that the value in the component gets populated..
When we then try to save the component it thinks that a mandatory field is left empty, and since the actual schema is defined as “minOccurs=1” it is throwing an xml validation error.
XML validation error. Reason: The element 'Link' in namespace 'http://xxx.xxxxx.com/abc/site/Link' has invalid child element 'renderType' in namespace 'http://xxx.xxxxx.com/abc/site/Link'. List of possible elements expected: 'uriClassification' in namespace 'http://xxx.xxxxx.com/abc/site/Link'.
Considering there are 4 content schema's in a schema-specific publication (e.g. 020 Schema Master).
When I attempt to go to my Content Publication, an create a new component, an XML error is triggered; which prevents successful save of a new component. I think its being displayed in these categories due to Tridion defaulting to a value that is not stored within the same publication as the category.
I am wondering if this is a product flaw, or a limitation depending on how you look at it. Its certainly not intuitive, regardless.
Has anyone else experienced this with