End users are entering duplicate data into different modules in Vista, specifically we've encountered the issue in the Job Cost module. This is because the database behind Vista uses a case-sensitive collation, which then allows the end users to enter Job123 and JOB123 as two different Jobs in the application.
This is causing data errors from our end users making mistakes on data entry.
Having the option to run Vista in a case-insensitive mode, using a case-insensitive database (SQL Server's default collation) or via application layer logic to prevent dupe data entry would be ideal. Then the customer can choose how to configure Vista on initial install, at least. (It appears a case-insensitive collation is the default that the Viewpoint Field Time system uses too.)
Guest
| Company | Haugland Group |
| Job Title / Role | Senior Software Developer |
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.
We also run into this issue with duplicated EM Equipment numbers. There is a workaround by using a trigger or possibly a validation procedure in Vista, but exposure via a UI checkbox would be ideal.