We'd like to accurately timestamp information in Viewpoint, and currently the closest we can get is by using either bDate or bTime, both of which use 'smalldatetime' which ignores seconds. This does not work so well if multiple events occur within one minute.
Is there any chance of a 'timestamp' datatype being added which mirrors datetime or datetime2 datatypes from SQL Server?
Thank you.
Company | Cutting Edge Plumbing & Mechanical |
Job Title / Role | Cutting Edge Plumbing & Mechanical |
I need it... | 3 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.
Viewpoint, I know this is not high on your priority list, but a way to properly handle fields that contain both a date AND a time would be a huge improvement!
Current workflow for custom table columns: After creating the table in VP, I go into SSMS and modify the column datatype to datetime2(0). Of course I have to redo this whenever the table is changed, but at least I'm capturing seconds!
Perhaps VP could think about adding the 'Precision' for date/time fields?
I'd imagine it going something like:
Or shoot, why not just let us type into the datatype field ourselves? As long as we could specify what kind of control to use (and the hidden data not seen in the control defaulted to the current system info), then I think we'd be fine. :-)
Of course to actually USE datetime fields we'd need a new date + time control, but I'm pretty sure .NET has you covered there.