-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 60
-
Fix Version/s: 61
-
Component/s: Content Views
-
Backlog priority:700
-
Sprint:nxNest Sprint 9.2.1
-
Story Points:1
The latest Studio version checks the presence of a schema. It displays the following errors in content views:
See validationError.png
A workaround is to use the following declaration in Settings / Registries / Document Schemas:
{ "schemas": { "ecm": { "@prefix": "ecm", "currentLifeCycleState": "string", "lockCreated": "date", "lockOwner": "string", "name": "string", "parentId": "string", "pos": "integer", "primaryType": "string", "uuid": "string", "versionLabel": "string" } } }
IMPORTANT
When using the workaround provided above, make sure that you do not select the "ecm" schema in the sort order afterwards but keep using the "system" option as usual. Otherwise once a fix will be deployed, if you remove this workaround from your registries you would end up with a validation error being displayed again (for a good reason this time!)
- is related to
-
NXS-3864 Add validation for missing properties when using the sort info editor
- Resolved