Versioning

Each Data app must have a version. The version enables you to update the app later, if needed.

Each app should stick to semantic version and always increase the major version if a breaking change is introduced. A breaking change is defined as the renaming of a type or field, or outright deleting it. A breaking change affects users that have already installed a data app, because they might have already used the specific data fields in their insight’s logic. If you just rename the field the insights that used the original name will stop working.

To add a version to the app, set the version property in the root of your Data app YAML file. For example:

{
    "version" "1.0.0"
}

NOTE: The Quantive Results platform supports schema migration. If you have to make a breaking change to your Data app contact the Quantive Results Developer Support team, and we’ll walk you through the necessary steps to migrate the schema.