Currently you have to recreate a matrix transmittal if you want to select 'Include private items within containers?' and 'Include non-visible items within containers?' It would be useful to be able to edit a matrix transmittal for this.
Gareth Blunden
| Company | Willmott Dixon |
| Job Title / Role | Design 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 understand why they don't allow this but again it's based on the completely false premise that Matrix Transmittals are used primarily to keep issuing complete lists of all documents, rather than Differences, which is what they should be all about, especially since it is Difference-checking that generates them (or is supposed to)!
It can't decide whether it's one thing or another - a complete register, or a difference notifier. VP need to choose one or the other and make all the functionality and database constraints fit one or the other case, not design the database constraints for one use case knowing full well it's being used for the other.