Here is the User Event Script
# suitescriptn
Nick
04/02/2019, 1:28 PMHere is the User Event Script
t
texmc
04/02/2019, 1:36 PMsetting fields on before load is a bit of hit or miss. based on your code try a couple of things:
1- your record var for the record object is using the same name as the module callback. try changing this to currRecord or something as this may be causing a conflict
2- if 1 doesn't work can you set the data in a scripted field and access and set it on pageLoad?
n
Nick
04/02/2019, 1:40 PMI changed number one but that didn't work. Not sure I understand number 2
t
texmc
04/02/2019, 1:42 PMdid you change this line as well if (record.type == 'customrecord_adb_eventlinup')
n
Nick
04/02/2019, 1:44 PMYeah i did
Nick
04/02/2019, 1:46 PMNo change. For the field I am trying to update, do I need to uncheck "store value"
c
cja
04/02/2019, 1:48 PMAre you completely sure that custrecord_kes_adb_json_event_lineup is the id of the field?
t
texmc
04/02/2019, 1:48 PMif it sets it and you don't need to persist it to the database then that is similar to #2, which basically sets the data temporarily
n
Nick
04/02/2019, 1:50 PMI need it to update that field and then when I run a search I need to get that data so I can add it to another record type
c
cja
04/02/2019, 1:53 PMI would avoid giving a variable the same name as a function parameter. In your case you are passing a param called record to the parent function and then declaring a variable called record within the beforeLoad function. I don't think it's causing you a problem yet but it won't help if later you want to use the parameter called record within beforeLoad
cja
04/02/2019, 1:54 PMPlease could you change lines 72 - 74 to as follows:
cja
04/02/2019, 1:54 PM Copy code
var eventlineupjson = JSON.stringify(eventdetaildata);
log.debug({
title: 'set custrecord_kes_adb_json_event_lineup to',
details: eventlineupjson
});
record.setValue({'fieldId':'custrecord_kes_adb_json_event_lineup', 'value': eventlineupjson});cja
04/02/2019, 1:56 PMThen make sure your logging level is set to Debug and run the script again and then look at the log
n
Nick
04/02/2019, 1:58 PM@cja got ya. Here is what the log returned.
Nick
04/02/2019, 1:58 PM Copy code
{
"lineup": [
{
"artist": "",
"host": "Blake Shelton - Host",
"count": "2",
"notes": "notes",
"order": "1"
}
]
}Nick
04/02/2019, 1:58 PMBut field was not set. Also, changed variable name
c
cja
04/02/2019, 2:04 PMAccording to https://3640472-sb2.app.netsuite.com/app/help/helpcenter.nl?fid=section_4407991781.html&whence= "Data cannot be manipulated for records that are loaded in beforeLoad scripts. If you attempt to update a record loaded in beforeLoad, the logic is ignored."
cja
04/02/2019, 2:06 PMUnrelated to your problem, in lines like the following, why do you enclose names in quotes?
n
Nick
04/02/2019, 2:06 PMAhhh so how can I update the field dynamically? Whenever the record is created or edited, I need to grab the line items and populate the custom field. That is why I treid before load
c
cja
04/02/2019, 2:06 PM Copy code
record.setValue({'fieldId':'custrecord_kes_adb_json_event_lineup', 'value': eventlineupjson});cja
04/02/2019, 2:06 PMSo why is fieldId in quotes?
cja
04/02/2019, 2:07 PMand value
cja
04/02/2019, 2:07 PMI don't think it matters as far as the effectiveness of your code, but it reads better without quotes
cja
04/02/2019, 2:07 PMI'm not a JavaScript expert so wondering if there's a reason
n
Nick
04/02/2019, 2:08 PMnot necessarily a reason honestly. I tend to do both sometimes.
c
cja
04/02/2019, 2:10 PM"how can I update the field dynamically" - could you do it when the record is saved?
n
Nick
04/02/2019, 2:13 PMI tried moving the code to an after submit but it didn't update that field
c
cja
04/02/2019, 2:17 PMIt would make most sense in after submit. It should be possible. Rewrite the code for after submit, test again and if you can't get it to work then paste here
n
Nick
04/02/2019, 2:20 PMSo I put a single log statement in the afterSubmit and it didn't even log that after I saved.
Nick
04/02/2019, 2:23 PMnever mind. I got that working. But still not setting that field.
Nick
04/02/2019, 2:35 PMGOT IT! For some reason it didn't like the afterSubmit, but it worked perfect on beforeSubmit
c
cja
04/02/2019, 3:32 PMRethinking what I said earlier, before submit is most efficient because it avoids having to save the record one more time to do your update
cja
04/02/2019, 3:32 PMSo I reckon you have the best solution now