Hey everyone. I switched jobs back in December and...
# suitescriptj
jackie.marler
04/17/2020, 9:57 PMHey everyone. I switched jobs back in December and I'm not working with NS anymore, but my old employer reached out because a script that I deployed doesn't seem to be working anymore. They can't nail down a date, but my guess is that it stopped working when 2020.1 was released. Is there anything in this script that jumps out as not supported? This runs when there's a field changed on the Shipping Method. It only runs when "Customer Pick Up" (internal id 16853) is selected. It grabs the SO's location, uses its address to create a custom shipping address, then uses it to set the Shipping Address on the SO.
jackie.marler
04/17/2020, 9:57 PMfunction setCPUshipto(type, name, linenum) {
if (name !== "shipmethod" || nlapiGetFieldValue("shipmethod") !== "16853" || nlapiGetFieldValue("location") == "")
{
return;
}
var locationId = nlapiGetFieldValue("location");
var locationLookup = nlapiLookupField('location', locationId, ['address.countrycode', 'address.attention', 'address.addressee', 'address.address1', 'address.address2', 'address.city', 'address.state', 'address.zip']);
var subrecord = nlapiCreateSubrecord("shippingaddress") || nlapiEditSubrecord("shippingaddress")
subrecord.setFieldValue("country", locationLookup['address.countrycode']);
subrecord.setFieldValue("isresidential", "F");
subrecord.setFieldValue("attention", locationLookup['address.attention']);
subrecord.setFieldValue("addressee", locationLookup['address.addressee']);
subrecord.setFieldValue("addr1", locationLookup['address.address1']);
subrecord.setFieldValue("addr2", locationLookup['address.address2']);
subrecord.setFieldValue("city", locationLookup['address.city']);
subrecord.setFieldValue("state", locationLookup['address.state']);
subrecord.setFieldValue("zip", locationLookup['address.zip']);
subrecord.commit();
}
jackie.marler
04/17/2020, 11:19 PMI think everything is working up until the commit. I threw some console.log's into the script and it looks like the locationId and locationLookup are correct.
jackie.marler
04/17/2020, 11:22 PMI'm not sure about the subrecord. I'll attach the log.
jackie.marler
04/17/2020, 11:25 PMConsole log for the CPU script
jackie.marler
04/17/2020, 11:37 PM@battk I think you helped with this script last June. Any thoughts on this?
b
battk
04/18/2020, 3:40 AMran the code, it sets the fields on the shippingaddress subrecord, but updates the fields after the transaction is saved
j
jackie.marler
04/18/2020, 3:41 AMit used to update the field immediately, which was the necessary solution.. they're running avatax, which requires that the field be correct when it's saved (for tax calculations)
b
battk
04/18/2020, 3:47 AMmight want to check if the tax are still correct
j
jackie.marler
04/18/2020, 3:47 AMHmm.. I don't think it's working the same for me. I entered an SO and had it use a shipping address in KS. Then edited the order, changed the method to Customer Pick Up, saved again. It did not update the shipping address on save.
b
battk
04/18/2020, 3:48 AMthe displays are wrong
battk
04/18/2020, 3:48 AMbut the address related fields should be set
j
jackie.marler
04/18/2020, 3:48 AMgotcha - let me try again
b
battk
04/18/2020, 3:49 AMtry something like
Copy code
nlapiViewSubrecord('shippingaddress').getFieldValue('addr1')battk
04/18/2020, 3:49 AMto check the data
j
jackie.marler
04/18/2020, 3:50 AMi realized my error in the previous test.. just did it again with different states, and you're absolutely right - the tax is updating by the display isn't
jackie.marler
04/18/2020, 3:51 AMi just printed the SO and it has the updated address, which makes sense - it pulls from the record
jackie.marler
04/18/2020, 3:52 AMi wonder why the screen isn't updating anymore.. even with an additional edit/change/save, it shows the incorrect address on the screen
b
battk
04/18/2020, 3:53 AMprobably check with netsuite support
j
jackie.marler
04/18/2020, 3:53 AMawesome thank you again