The HR Resource HRRM.MidName field should be longer as there are several employees with more than one legal middle name or an extended middle name. Right now we do not have enough room to accomodate these instances.
Kylie Willoughby
| Company | B&D Industries, Inc. |
| Job Title / Role | Analyst |
| I need it... | Yesterday...Come on already |
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.
The other part of our quandry is at data entry, getting staff to be consistent with multiple names, if they can fit in the middle name field. We should not use it, even if it fits, just for consistency. This is difficult given the many variables.
I am aware that I can change it. I agree with Gary that it is not advisable to do so. I am asking that Viewpoint undertake this so it is permanent and useful across the system. Alternatively, we could use Vista's VA/UD to add a field, but you would need to re-work all the reports, and the tax stored procedures still wouldn't use it, again, a lot of work and not advisable in this circumstance.
The change in the length of a typical name has changed by 30%, according to my anecdotal experience, over the past 15 years. Relatively recent, but we know it is here to stay and we, as developers, accountants and record keepers, need to accommodate this in order to maintain the accuracy and integrity of our records.
Changing the field length as described (via direct access to the Vista tables using SSMS) while doable, is not recommended. In this limited case it's not likely to have a negative impact, but be aware that other SQL objects (procs, triggers) along with UI presentation and reports will not be aware of the new field length.
You can fix this yourself. All you need to do is change the varchar limit from the system default to the desired length. I believe this is 15 by default, you will need dbo access granted from VISTA 1st so maybe you need your IT team involved. Just log into your SSMS with the user granted dbo status and you can change the lengths for any VISTA Table as needed.