Timeline for Process of Validating components against their schema
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2014 at 12:56 | vote | accept | BVL | ||
| Jan 30, 2014 at 12:55 | comment | added | BVL | Ok. Validate button on GUI, checks only the XHTML field's XML validity, while the core service validateXml really validates the whole component agains it's schema definitions, including mandatory fields, etc. Thanks! | |
| Jan 30, 2014 at 11:38 | comment | added | Andrey Marchuk | ValidateXml will check for all fields and metadata | |
| Jan 30, 2014 at 9:54 | comment | added | BVL | now I understand. That validatexml only checks for the certain field types, where we can add XHTML. It can tell if the entered code is XML or not...Also the VALIDATE button on GUI checks only the same. I'm asking about checking against the Schema file of a content component, checking all fields, metadata etc. of a certain content component. As you know a schema file can be changed anytime, which means the old contents may become invalid agains the new changed schema file. For example if we add a new mandatory field to a schema but old components doesn't have that field-> it gets invalid then. | |
| Jan 30, 2014 at 9:46 | comment | added | Likhan |
In the UI there is a button Validate that should do the trick.
|
|
| Jan 30, 2014 at 9:35 | comment | added | BVL | Hi! Thanks! is this core service available for SDL Tridion 2011 too? Is there a way on GUI to trigger this function? | |
| Jan 30, 2014 at 9:30 | history | answered | Andrey Marchuk | CC BY-SA 3.0 |