Current issue: Create a stored procedure (using SQL Studio Manager) with four arguments (two inputs, two outputs).
Assign it to a field in VP as a validation procedure, map the arguments, and all works as expected.
Now, MODIFY the stored procedure by removing one of the output arguments (inside SQL Studio Manager), so it now has three arguments.
No matter what you do after this within VP, you can not use that stored procedure properly. If you supply three arguments, it complains you supply too many. If you supply two arguments, it complains that the procedure expects a third. If you supply four, it says too many as well. Sometimes it does not complain, but there are no results from the procedure (as if it didn't run)
But if you make AN EXACT DUPLICATE of the stored procedure and assign it to the field in Viewpoint, everything works again. Confused? So am I! Apparently VP is caching the "required arguments" for the stored procedure somewhere, and not updating them when the real stored procedure updates.
My hope is that the Viewpoint Team will update their code to update that secret cached table of requirements whenever the stored procedure is assigned to a field, instead of only updating it the first time a stored procedure is assigned to a field. This would save us as developers a lot of time.
In a perfect world we would make no coding mistakes. I'd like to move there someday!
Nathan Sutherland
| Company | Cutting Edge Plumbing & Mechanical |
| Job Title / Role | Cutting Edge Plumbing & Mechanical |
| I need it... | 1 month |
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 just started digging, it doesn't appear it caches it. I thought it did to as I have experienced the same thing.
My work around is that I remove the validation procedure, close the form reopen and try again.
exec vspDDGetParamList @objname=N'uspEMInsuranceType'
That calls
SELECT param.name AS [ParamName], ISNULL(baset.name, '') AS [SystemType], param.is_output AS [IsOutputParameter] FROM sys.all_objects AS sp INNER JOIN sys.all_parameters AS param ON param.object_id=sp.object_id LEFT OUTER JOIN sys.types AS baset ON baset.user_type_id = param.system_type_id and baset.user_type_id = baset.system_type_id WHERE sp.name=@objname