Skip to content

Revision Configuration#

The Config sheet has specific configuration regarding the format of the revisions that will be created in the system from the versioned entities that are described in the package. Three fields are vital for compliance with the object naming scheme and you can find details on each of them below:

Revision Format#

This configuration defines the way of appending a revision to a name.

The default value for this field is [RevisionName], which means that the [ and ] are delimiters of the revision name. A versioned entity will be created in the system like this:

Entity name Revision name Revision format field Entity revision name
Chocolate Chip Cookies A [A] Chocolate Chip Cookies [A]
Chocolate Chip Cookies One {One} Chocolate Chip Cookies

Table: Entity revision name format

Note

RevisionName is a mandatory field in the config sheet and it must exist at least one non-empty character on each side of RevisionName.

Use Revisions#

This configuration defines whether the Master Data Packages will use revisions. The three possible values are:

  • Yes - the Master Data Packages loader will attempt to parse the revision value from the name field of every row of a versioned entity sheet. If the revision is not found, it will throw an error.
  • No - the Master Data Packages loader will not parse any revision. If a cell declares ProductName [A] as name for a versioned entity, the loader will assume that the name of the object is explicitly ProductName [A] and not that the entity is called ProductName with revision A.
  • Optional (default) - the loader will try to parse the revision but no error will be thrown if the revision is not found.

Default Create#

This configuration defines the default operation when creating an object which already exists. The two possible values are:

  • Create Version (default) - if the entity already exists, create a new version of that object.
  • Create Revision - if the entity already exists, create a new revision of that object.

Note

If the name of the entity is ProductName[A] and an entity ProductName with revision A exists, the system will create a new version for that revision. In this case, the create operation is independent of this config.