Your feedback is an essential part of how we continually improve ProjectSight. You can use this page to submit new ideas, or vote on ideas from other users.
This portal is for suggesting enhancements only. If you are experiencing a product defect, please contact support.
Ability for Drawings to be unpublished to correct any item, such as a Drawing number being incorrect.
Users wants to be able to correct a drawing number that may have been interpreted wrong on a published drawing and not lose revision information.
Currently, they have to delete the drawing and re-upload and re-publish losing any revisions
Suggested implementation:
Give the users the ability to unpublish and re-publish to correct items such as drawing number.
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.
A shift towards the importance of drawing revision would be beneficial for my group.
I upload drawings with their own revisions with various characters. ProjectSight likes to assign a revision itself as a revision to being on ProjectSight indexed at 01 - not the actual drawing revision. My group needs the actual drawing revision to be automatically OCR recorded.
from an admin posted yesterday in one of the merged ideas:
AdminMichael PetersonReply | Oct 1, 2024
Hi Chris,
We're working on this now, I've merged this to a similar suggestion that covers this functionality. Looking forward to delivering it soon!
this would be great
One should be able to upload a previous revision number without having to delete all sets that have been uploaded and are further sets than that one. For example, if I have Revision 5 uploaded but have not yet uploaded Revision 4, I should be able to edit the currently uploaded Revision 5 set and upload the Revision 4 set in a manner which does not require the deletion and reupload of Revision 5. One should simply be able to edit published drawings and change the set they belong to; this is an easy fix.
I want to be able to edit the revision numbers on drawings that have been uploaded. Right now, I would have to delete these drawings and republish them to achieve this.
This issue regarding the inability to edit published drawings was first uploaded in May 2019, and it still has not been addressed in in August 2024. This is a very basic feature that should have been addressed before the product's launch.
This issue was first uploaded in May 2019, and it still has not been addressed in in August 2024. This is a very basic feature that should have been addressed before the product's launch.
Comments from a client at Barr & Barr:
There are going to be occasional read errors that are not caught before publishing. In your competitor, PlanGrid, when this happens you can go back and fix the source of the error, and it makes the corrections in all subsequent versions of the drawing. That is the way it should be.
In ProjectSight, you can’t make edits to drawings once they are published. So I had to go back to the drawing set where the read error originated, and delete the drawing and re-upload it. But when I did that, it transposed the Revision Number of that drawing and its subsequent revision, making the drawing with the more recent revision date Rev. 0, and the older drawing Rev. 1. Apparently this happens because ProjectSight bases Rev. number on Rev. date except in this particular circumstance, where is bases Rev. number based on which drawing was uploaded more recently. Or maybe I am misremembering what I was told about how ProjectSight determines what is the most recent revision of a drawing. It should be based on Revision Date, not which drawing was uploaded most recently.
So the only way to fix this was to go back and delete the drawing where the read error originated and every subsequent version of that drawing (and in this case there was only one subsequent version, but there could have been ten), and then re-upload them in the order in which I wanted the revisions to display.
In PlanGrid I would just go back to the set where the read error occurred, correct the error (which I was able to do without even having to delete and re-upload the drawing), and all subsequent revisions would be automatically corrected. In ProjectSight I had to do that whole convoluted process described above. No one in their right mind could possibly think that this is an intuitive and user friendly process, and how it actually made it past beta testers is baffling.
Good afternoon,
I have a similar predicament, I had a published progress set of drawings, which was used to issue contracts but once the Master Permit set was released, we needed to relabel the Revision tag in order to accommodate the new set and keep the sequence.
The only solution available is to delete all drawings and reload, which causes a massive delay, sometimes the sets may have over a 1000 sheets.
Please provide an efficient solution that will allow users to modify certain details without compromising the records.
Thank you