Need to add a field for udADUserID to the 'Initialize to Vista' options. There is a key restraint on the table bHRRM that prevents the field udADUserID from being Null or have duplicate values. We would like to be able to write data to that field when Initializing to Vista so that we can utilize this function without turning off the key restraint on the table.
Travis Rider
| Company | Clyde Companies |
| Job Title / Role | Sytem Administrator |
| 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.
© 2024 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.
We wrote a query to get all the answers to our custom On boarding Forms and are passing all that data into ViewPoint using the OnPostInitAction. It would be nice if they made it easier to map the items we collect in the custom forms to ViewPoint tables and columns, but a simple cross reference works well enough. The nicest thing about it is by the time it ONPostinitAction is called, the EE record exists in HRRM and has an Employee number which makes it easy. You do need to give some thought to how you collect and update the information, but it's pretty straight forward if you have SQL skill available to you.
Hi Darren,
The initialize to vista has a post action script that can be run. You can create a stored procedure named ONPostInitAction that will be run as part of the initialize to Vista. This procedure has one input, @OnboardID. Using this procedure, your team should be able to accomplish the tasks they need.
Regarding the trigger constraint, the user defined field being required is not something that the portal can accommodate out of the box. We recommend that your team does not use a trigger for this. Instead, use a Vista validation. This will allow the portal to create users and fill in the ad account using the ONPostInitAction while maintaining the ability to prevent users from saving a new record in vista without keying the field. The trigger is not needed if implemented as described above. If you need assistance with the stored procedure or validation, professional services can take care of it for you.
Best
So the enhancement request we are asking for is that the "Initialize to Vista" tool in Onboarding Dashboard, behaves in a similar manner to "Manage Request Settings"--the ability to choose from any field in HRRM and add it to the "Initialize to Vista" pop-up modal form, not just limited to the 13 fields KDS has enabled. This will help the HR staff when onboarding new hires, to get as much as they can into Vista HRRM at the time of onboarding. One major one Travis has mentioned above, is the Active Directory User ID that we have for the employee, into a custom user defined field in HRRM. We want to write that to HRRM for the employee, among other things, when we click, "Initialize to Vista."