Trimble Connect Knowledge Center

File versioning is extremely useful, not just for keeping folders tidy, but also because by looking at the Modified On dates I can see if I'm missing an update from someone. However, it is problematic that Trimble Connect creates a new file version when a file is only moved between folders within Connect--and therefore a new Modified On date and Modified By user. This creates a false history of that file; simply moving it does not change its contents, so it shouldn't be considered a new version. Certainly show that the file was moved in its history, but please don't have every movement of that file create a new version and Modified On date. 

For instance, if a modeler posts a file to the wrong folder, I can't move it because it makes a new version and changes the modified date and user name. Someone looking at the project unfamiliar with this process might wonder why I was modifying and making an new version of someone else's model, when I was just trying to be helpful and proactive. Now I have to delete the erroneous file, email or call that person and wait for them to re-post their model to the right folder. It's an unhelpful feature, and even has the potential to create liability for me since it appears that I changed a file from outside my company. 

I completely agree with your comment. This functionality, as it is designed, creates misunderstandings.

My suggestion for the theme is that this should be solved in the functions of "File attributes".

Almost everything is arranged so that you can manage the history of the files with "file attributes". 

Unfortantly the development stoped before the most important functionality was added - customizable file attributes to different projects.

If the functions in "file attributes" had supported project-adapted properties, it would be a very good solution. today, Trimble has stopped the development of "file attributes" before the opportunity to adapt for different types of projects.

For example do we in our company have well over 100 different projects in our TC account. And therefor we can not have same file attributes to all 100 project. So, as it is now, we can not use the functions in "File attributes" to solve the tasks you describe here in our projects