Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

{ "validationErrors": [ { "message": "Ambiguous ids. There are 2 property type definitions with the id 'tenDefault:from'.", "serviceErrorCode": 2110 }, { "message": "Wrong base id. The base id of the system:document type definition 'tenDefault:email' must be 'system:document', but it is 'system:folder'.", "serviceErrorCode": 2131 }, { "message": "Invalid property reference 'fromm' in type definition 'tenDefault:email'.", "serviceErrorCode": 2132 }, { "message": "Invalid secondary object type reference 'appAcl:aclowner' in type definition 'tenDefault:email'.", "serviceErrorCode": 2135 } ] }
As of Versionproduct version 1.0 | component version 1.0
Request MethodPOST
Response FormatJSON
Required Permission

available if listed in authorization.accesses in authentication-prod.yml and the specified access condition is matched.

>> AUTHENTICATION Service
DescriptionThis endpoint is used to update

Update the tenant schema

. Similar to other schema update endpoints in yuuvis®, this infers a schema validation and returns its results to the user, performing the schema update only after successful validation

for the tenant which the requesting user belongs to. The new schema is passed in the request body in XML format and is validated before the update is executed. Thus, it is not possible to introduce an invalid schema via this endpoint.

For details and examples regarding request and response please visit Schema - Defining Object Types.

Request HeadersContent-Type: application/xmlResult Example

The result is a JSON structure containing a validationErrors list, which can also be an empty list.

Code Block
title200 - no validation errors, the schema has been updated
{
    "validationErrors": []
}
Code Block
title422 - there were validation errors, the schema was not updated