We bill our clients Cost + Fee. To accurately enter JC Revenue Projections, the Projected Cost must match the Projected Revenue on every row except the last line where we enter our fee. If you go to the Options tab, there is a tool called Calculate Projections where you write over the plugged values using Projected Cost. This is great but it doesn't correctly calculate the Projected Contract unless the Plugged box is checked. THE SYSTEM DOESN'T LET YOU CHECK THE BOX MANUALLY! I have to overwrite what is in the Projected Revenue column with the exact same number and then it will check the box and then the Projected Contract dollar amount is correct.
Please fix this!
Many thanks
Diane Dalton
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.
Please fix as soon as possible! Thank you.
This is crazy, you would think this loophole would have gotten rectified before now. C'mon Development team, this really needs to be addressed and fixed!