Does anyone get any weird validation errors lately...
# sdf
f
Does anyone get any weird validation errors lately? I am getting
Copy code
An error occurred during custom object creation.
Details: Fail to evaluate script: {"type":"error.SuiteScriptModuleLoaderError","name":"FAILED_TO_VALIDATE_SCRIPT_FILE","message":"Failed to validate script file: Invalid JSDoc tag value; valid values are: @NApiVersion [2.X, 2.x, 2.0, 2.1]","stack":[]}
referencing a XML file for a restlet. However the JSDoc for the JS file referenced in that error has
Copy code
/**
 * @NApiVersion 2.1
 * @NScriptType Restlet
 * @NModuleScope SameAccount
 */
as the first 5 lines
k
Check any libraries as well as validation can fail on things you have in your define
this 1
f
we deploy the same codebase to multiple bundles
and they all went through but let me check
hmm could be something like this
Copy code
/**
 * @NApiVersion 2.1
 * @NModuleScope SameAccount
 * currency.js - v2.0.3
 * <http://scurker.github.io/currency.js>
 * Copyright (c) 2020 Jason Wilson
 * Released under MIT license
 */
cause an issue?
k
Could be. But would be more likely that a NApi Version is wrong
f
Hmm no they all look correct
I checked them all they all ether say
2.1
or
2.0
k
Pass. Could remove all your NApiVersioning from all your libraries as it’s not actually required.
We don’t record the NApiVersion in a module anymore only in the entry point scripts.
We have converted all our scripts to 2.1 now as it is backwards compatible.
f
We have a couple of entry point scripts in 2.0 as Netsuite only supports 2.0 for them... But the question still stays: Why do they same scripts deploy for one SuiteApp without issues but fail for this new one we try to deploy
exactly same scripts
k
Pass. Without testing myself it’s hard to debug.
Is it trying to update the deployment or is it a brand new deploy?
f
brand new deployment
k
Odd
f
Yeah I know which is why I was wondering if its just the typical netsuite release rollout that is causing all sorts of strange issues (regardless if the account is already on new version)
k
Possibly. Haven’t got a leading account myself at the moment as messed up my SDN request for an account
So could have same problems when I test mine in the next leading account.
f
Its on a trailing account. But in the past we saw strange behaviour even in our trailing accounts during this time
k
Maybe something has been updated. Sorry can’t really be of anymore help without trying to deploy myself.
f
No worries. Thanks for trying. maybe someone else has an idea/seen something like that
Ok I've opened a support case for now
Oh actually you where right. I found a script that because of a merge instead of
2.0
had
2.2
...
I guess the other bundles had it deployed when it had the correct version applied which is why they never showed the error till we did a brand new deployment
It would be so much more helpful if netsuite would have show the invalid value...