Afternoon. Anyone come across this error message "...
# suitescript
n
Afternoon. Anyone come across this error message "ReferenceError: rateSlaveCondition is not defined". This happens on an Estimate when setting the item field on the item line via a Client script and using setCurrentSublistValue. The record being created is set to dynamic. The script is set to 2.x but we've also tried setting it specifically to 2.0. Disabling the script and setting the field via the UI does not error. All other scripts and workflows have been undeployed. It feels to me like NS's code is using "strict" but missing a value. We did try including ignoreFieldChange:false even though that's the default but that didn't help.
c
there's a property thats not really used much but you can try it. When setting the sublist value, set forceSyncSourcing = true.
n
Awesome will try thank you @creece
c
It may/may not work. Ive had some weirdnesses like what you mentioned before and it solved it at least. Otherwise, I am not sure.
n
Yeah tried it and it didn't work but appreciate you replying and worth keeping in mind. Curiously it's a script that was originally SS1.0 and worked fine but is failing in SS2.x My colleague has been working on this for a few hours and we're starting to think we might need to get the dreaded NS Support involved.
c
No problem. Have you tried non-dynamic mode just to see? It will require a little refactoring most likely to test
n
Yes tried setSublistValue / non-dynamic. It's one of those "makes no sense" situations that swallow up time and will no doubt result in some odd solution that makes less sense. netsuite
c
I would not doubt that.