ClientVersionPrecision
This parameter is not applicable to Planning Analytics Engine.
Parameter type: optional, dynamic
The ClientVersionMinimum and ClientVersionMaximum parameter values are expressed as a version string using the following format:
m.n.ttttt.iiiii
Where:
m = major release number
n = minor release number
ttttt = maintenance release number
iiiii = interim fix number
Using this format, the version string 11.8.02000.7 indicates major release 11, minor release 8, and maintenance release 0.
If ClientVersionPrecision is not set in the Planning Analytics database configuration or if it is set to 0, only the major release number, minor release number, and maintenance release number are used to enforce compatibility between client and database. In this case, any client from major release 11, minor release 8, maintenance release 0 and more recent can connect to the database.
You can enforce more precise database and client version compatibility by adding ClientVersionPrecision to the Planning Analytics database configuration and setting the parameter to one of the following values.
- 1 - Indicates that the maintenance number will be enforced, but not the interim fix number.
- 2 - Indicates that both the maintenance number and interim fix number will be enforced.
Examples
If ClientVersionMinumum = 11.8.02000.7 and ClientVersionPrecision = 1, only clients from major release 11, minor release 8, maintenance pack 0 or later can connect to the database.
If ClientVersionMinumum = 11.8.02000.7 and ClientVersionPrecision = 2, only clients from major release 11, minor release 8, maintenance pack 0, and interim fix 7 or later can connect to the database. In this case, the interim fix numbers are enforced when determining database/client compatability.
Finding the Planning Analytics build number
- Go to \tm1_64\bin64\.
- Open the tm1appapi-winx64h-app-##.#.#####.# file.