Collaborate with Viewpoint and your peers by providing us with your input
We have had it happen that a sub project gets added on a regular project after setup and after costs are posted and currently there is no way to do this without having to create new master and sub projects and then transfer all the costs to the newly created projects.
Bob Arnett
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.
This needs to be added as an option, run into this often,
Linked in knowledge-based article named "Master and Sub Project Setups".
We run into this frequently when we issue a single bid and are verbal award and/or LOI, then when the contract comes it's split into 2 or 3 individual contracts. We may have start up costs that require setting the job up prior to receiving the contract, then realize it needs to be split in 3 or more jobs. We've paid to have scripts written to merge standard projects or sub-projects under a master in the situation. This functionality would help us tremendously.
I agree with Bob Arnett. It is very frustrating that you can't change jobs from a regular job to a master job. One way to help eliminate that would be to limit who could change the status of the jobs in the admin set up section of PCMX.
Allowing projects to be changed after they are created could open the door to many risks, and would require careful design and careful use by the end users. One option that exists is to set up any project that you think may later get sub projects as a master project - you could even just set up all projects as master projects, and then if a subproject arises for it, you could create that one as a sub project and link it to the appropriate master. There are really no differences between a master project and a standard project, other than the ability to link sub projects to a master but not a standard project. The one area to pay attention to here, though, would be when you run reports, to be sure to include master projects, and then you can save that report parameter and not have to focus on it again.