< class="prominent-subhead ">

After upgrading to K2 Five, custom Environment Variables set to a field type of "Category Server" will be overwritten

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


After upgrading to K2 Five or K2 5.1, as well as when running the K2 Setup manager, you will see that some environment variables were overwritten. Specifically, any of the type "Category Server" that does not hold the default connection string value.






- Previously these values were not overwritten on 4.7 or an older version of K2.

- Running Configure or Repair with the K2 Setup Manager will also overwrite these fields.

- Applications using these specific environment fields, are now running into issues as the value has been updated.


When you create custom environment variables, they should be set to type "Miscellaneous Field".


If the Environment Fields are set to this Field Type, they will not be touched when Upgrading, Configuring, or Repairing K2.

On K2 Five and 5.1, if K2 sees a Field type of "Category Server" but the value is not in the expected connection string format, it will overwrite the value to be the default connection string. For organization's sake, this would be the proper Field Type as the values are in fact not related to the category server in any way.

If you have already completed the upgrade and seen this behavior it is recommended that you roll back to before the upgrade and update the Field Type to be Miscellaneous Field instead of Category Server. Then you should do the upgrade again and the fields will not be overwritten.
If a rollback is not available you will need to manually update these Environment Fields to be the desired value and Type of Miscellaneous Field. K2 does not have an audit trail for what the values were set to before.

This has been identified as a known issue within the K2 product.