SyncronizedEPTDocumentSave Method Content Studio 5.7 SDK
Content Studio Web Content Management System

[This is preliminary documentation and is subject to change.]

Saves the content of the document loaded. If the document does not exist it will be created, otherwise it will be updated.

Namespace: ContentStudio.Document.EPT
Assembly: CSServer5 (in CSServer5.dll) Version: 5.7.5016.0 (5.7.5016.0)

public virtual void Save()

CSExceptionA business rule was violated in the underlying Content Studio database
ArgumentOutOfRangeExceptionA value was passed in that lies outside of the acceptable data range.
SqlExceptionAn error occurred when executing the command against the Content Studio database
NullReferenceExceptionA string parameter was null and the parameter does not accept null values
ArgumentExceptionOccurs when creating a new document: documentName cannot be null or empty
InvalidOperationException Occurs only if schema binding is enabled and ValidateOnSave is false.
The number of fields does not match the number of fields specified in the schema
Cannot save. The field "%FieldName%" does not exist in the EPT schema.
XmlSchemaException When schemabound and ValidateOnSave is true and the data set does validate against the Ept schema.
Content Studio permissions

WRITE permission on the document is required.

This method does not approve (publish) or check in the document, nor does it offer a possibility to change any of the document's properties.

Note Note
The behavior of this method changed in Content Studio 5.2. Prior to version 5.2 Save sends the entire Ept document to the underlying CS API but in version 5.2 only the fields that are changed is sent. The underlying Content Studio API ensures that all fields are saved anyway. This change solves some issues with the Server Side validation that could generate validation errors in some cases even though the field that caused the validation problem was not changed.
See Also