Hello, everyone. Please advise on the best practic...
# suitescript
z
Hello, everyone. Please advise on the best practices for updating the API version of a script record and ensuring that the updated version is used. Attempts to update the script record programmatically are failing.
b
the api version is specified in the script file
z
Updating the JSDoc does not update the api version in the UI for the script record.
b
it should unless whatever you are using to do the update isnt triggering script parsing
try making the change via the ui first
z
Can you elaborate on making the change via the UI? The script is included in my SuiteApp and I am seeking solutions that are scalable and reliable. I have made the relevant change in the IDE and uploaded the new file to the target account, updating the file, but not the
apiversion
on the script's record. I have made the relevant change in the IDE and deployed the project to the target account, updating the file, but not the
apiversion
on the script's record. I have attempted to programmatically manipulate the
apiversion
using
record.submitFields()
in an SDF Installation script, no change is noted to the script's record. Despite one or more of these options working in the past, the only method that has worked as of today is manually replacing the script file in the UI. This allowed me to go
2.0
to
2.1
but did not allow any subsequent changes (e.g.
2.1
to
2.0
). Hopefully, this offers some additional, meaningful context 😅
Also, thanks for the quick responses @battk -- it is greatly appreciated.
b
as in find the file in the ui
find the edit button associated with it, and then make your change