When you have two versions on the same file but different file names/dates registered in a container or project it would be very useful to be able to browse to the older file within VP and pull it in behind the latest version instead of having to upload from outside the enterprise.
I had a consultant link a notification to a version 3 of a drawing, ( that has no precedent files behind it in properties) but version 2 was sitting in another container. I couldn’t merge version two in behind v3 without first deleting 3, revising v2 with a copy of v3, but also breaking the link to the transmittal. I suppose the closest solution would be to load v2 as a secondary file but it’s not actually a secondary version of v3.
Seems odd to me that you can have registered files within viewpoint but they cannot be merged for the purpose revision when needed.
Geoffrey Stewart
| Company | Octa Associates |
| Job Title / Role | Senior Project Manager |
| I need it... | 12 months |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.
© 2023 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
I have been after something like this for ages. Or just be able to have a 'Merge' command available in the 'Actions' menu, where you see a container tree menu appear that allows you to select any container that contains an item with the same Name. Then, that will combine the audit history of the two items into the target item.
What I often find when I join a new company/project is that QSs have uploaded Drawings in subcontainers called 'Tender', 'Preliminary' and 'Construction', then begin linking drawings from a combination of these into a Static Virtual Container. Then they create Dynamic VCs for Work Packages and then the drawings start getting revised in the various locations, instead of each drawing just being in one location with one audit history and one place in which the Virtual Containers can be linked from.
I'm finding I have to perform this silly routine of downloading all drawings from all subcontainers, all revisions, export all Virtual Container contents into CSV files, delete all drawings, the extraneous subcontainers, then start re-uploading everything in chronological order, including when the Virtual Containers were created, so I can upload each revision and add each Virtual Container link in the same order they were originally created, but linked to an individual instance of each drawing, which I then revise as I get to the subsequent revisions that were previously downloaded from different containers.
All just to keep the correct links from the Virtual Containers and to leave just one place for each drawing to be revised in future.
I hope from what I've written it's clear how crazy this is, when it ought to be possible to just merge once instance of any given 'Name' value into another container that has the same 'Name' value.
Yes, if workflows are different between one container and another, the usual warning message will need to be appear, but so what? That's just the same as doing a 'Move' operation, which works fine if the 'Name' is not the same, but not if they are.