Just curious if anyone have experienced attaching ...
# suitescriptw
wbermudo
11/05/2021, 5:05 PMJust curious if anyone have experienced attaching a client-side script 2.x or 2.1 on a Suitelet using clientScriptModulePath where the there is fieldChanged entry point, and then when the fieldChanged is triggered it is passing 3 arguments (sublistId, fieldId, line) instead of a context object that has those properties? I am getting this behavior right now.. is this a defect?
s
stalbert
11/05/2021, 5:06 PMyes, I believe this was mentioned recently, though I thought it only applied to 2.1 scripts?
stalbert
11/05/2021, 5:06 PMit was as if the client script was being invoked as if it was SS1.0
stalbert
11/05/2021, 5:07 PMI'd recommend searching this slack as it was recent enough to probably be still resident in the chat history?
w
wbermudo
11/05/2021, 5:07 PMYeah, I converted it back to 2.x and had the same result they were pass as arguments.
Yes, you are correct - it's like it's invoking as SS1.0, really strange.
wbermudo
11/05/2021, 5:08 PMOk, thanks @stalbert! appreaciate the quick response and confirming my sanity ahah
a
alien4u
11/05/2021, 5:12 PMClient Scripts 2.1 that do not require a deployment are not behaving correctly at the moment, too many random shenanigans or behaviors, I would recommend to stick with 2.0 for any Client Script that does not requiere a deployment.
👍 2
s
stalbert
11/05/2021, 5:29 PMthe ironic thing about this is Browsers have been a natively 2.1 compatible environment for many years now 🙂
4 Views