Data versioning

Data and metadata values are versioned independently of their parent record.

The Attribute data version is related to the record version, and can be considered a sub-feature of the record version

Each Attribute data value in a record has a version number that is incremented if the data value has been changed since the previous version of the record was released.

Between different versions of a record, the data for any specific Attribute may be unchanged, and therefore the same version of the data may be shared by multiple record versions.

Example: a record with eight different versions, might have only three versions of data for an Attribute:

Record version	1	2	3	4	5	6	7	8
Data version	1			2			3

The data version number may lag behind the record version number. It will never be greater than the record version number.

If version control has not been enabled for a table, none of data in the table has a version number.

Attribute data values do not have a version state.

The data life cycle

Action	Description
Adding a new record	When the data is created in the Unreleased record, it is given a version number of 1.
Editing an Unreleased record	The data version number in an Unreleased record is only incremented once, the first time the data is changed. After that, the data may be edited multiple times without incrementing the version number with every subsequent edit. Editing the metadata for an Attribute does not affect the version number of the Attribute data, only that of the metadata.
Releasing a record	When the record is released, the value for that data version is fixed. The data version number is not incremented.

Viewing data version information

You can view information about the data in each version, including the data version/record version and the date(s) when changes were made from the datasheet View menu: click View>Version information.

For example: