Tosca Commander Versions should not be intermixed when connecting to a Common Repository
This article helps you mitigate Tosca Worskpace issues when upgrading to new versions of Tosca Commander.
After users connect Tosca Commander 12.1 to a shared project and Check In objects, it is possible that previous versions of Tosca will no longer have the ability to Update All, or Check Out, etc. If this happens you will see the following error:
Attribute "ExternalFileId" was not found for type "FileContent". Please verify that the Tosca Setup is complete and all the AddIns are installed. Do you want to try again?
Attribute "ProvidesNamespace" was not found for type "TCConfiguration". Please verify that the Tosca Setup is complete and all the AddIns are installed. Do you want to try again?
DO NOT INTERMIX VERSIONS OF TOSCA IN PRODUCTION ENVIRONMENTS
As of writing, Tosca Commander has been on the same DB schema from 11.1-12.1. Thus, even though it is possible to connect to the same Multi User project using different versions, it is advised to refrain from doing so as some object attributes may be altered with new Tosca versions.
In case your project no longer functions from a workspace from 12.0 or earlier, you should first try to create a brand new workspace connected to the same DB to see if the issues are resolved. If not, upgrading all Tosca Commander clients to 12.1 will work as intended.