function setCPUshipto(type, name, linenum) {
if ...
# suitescriptj
jackie.marler
06/03/2019, 1:19 PMfunction setCPUshipto(type, name, linenum) {
if (name !== "shipmethod" || nlapiGetFieldValue("shipmethod") !== "16853" || nlapiGetFieldValue("location") == "")
{
return;
}
var locationId = nlapiGetFieldValue("location");
var locationRec = nlapiLoadRecord("location", locationId);
var subrecord = nlapiCreateSubrecord("shippingaddress") || nlapiEditSubrecord("shippingaddress")
subrecord.setFieldValue("country", locationRec.getFieldValue("country"));
subrecord.setFieldValue("isresidential", "F");
subrecord.setFieldValue("attention", locationRec.getFieldValue("attention"));
subrecord.setFieldValue("addressee", locationRec.getFieldValue("addressee"));
subrecord.setFieldValue("addr1", locationRec.getFieldValue("addr1"));
subrecord.setFieldValue("addr2", locationRec.getFieldValue("addr2"));
subrecord.setFieldValue("city", locationRec.getFieldValue("city"));
subrecord.setFieldValue("state", locationRec.getFieldValue("state"));
subrecord.setFieldValue("zip", locationRec.getFieldValue("zip"));
subrecord.commit();
}
b
battk
06/03/2019, 1:22 PMyou would need to change every line that has location rec on it
battk
06/03/2019, 1:23 PMinstead of loading a record using nlapiLoadRecord, you would use one of the search related apis
battk
06/03/2019, 1:23 PMi recommend nlapiLookupField, its the closest to loading a record
battk
06/03/2019, 1:24 PMthe first 2 parameters to nlapiLookupField are the same as nlapiLoadRecord, its the record type and the internal id of the record
battk
06/03/2019, 1:24 PMthe third parameter is an array of column
battk
06/03/2019, 1:25 PMnormally I would say make the array a list of the field ids
battk
06/03/2019, 1:25 PMbut this will end up being a case where the search columns and record field ids don't match perfectly
battk
06/03/2019, 1:28 PMthis would normally be the part where you have to build the search in the ui to find out column names / use the suitescript record browser
battk
06/03/2019, 1:28 PMill save you the trouble, your nlapiLookupField should look like
battk
06/03/2019, 1:28 PM Copy code
var locationLookup = nlapiLookupField('location', locationId, ['address.countrycode', 'address.attention', 'address.addressee', 'address.address1', 'address.address2', 'address.city', 'address.state', 'address.zip']);j
jackie.marler
06/03/2019, 1:29 PMso i'm replacing the var locationId = nlapiGetFieldValue("location";
jackie.marler
06/03/2019, 1:29 PMbecause without edit access, that doesn't work with restricted roles, correct?
b
battk
06/03/2019, 1:30 PMyou would leave the locationId in place
j
jackie.marler
06/03/2019, 1:30 PMah ok
b
battk
06/03/2019, 1:30 PMyour script won't be able to load the record, but you can get and set the location
battk
06/03/2019, 1:30 PMjust like in the ui
battk
06/03/2019, 1:33 PMlocationLookup should be an Object that looks like
Copy code
{
"address.countrycode": "US",
"address.attention": "lorem",
"address.addressee": "ipsum",
"address.address1": "dolor,
"address.address2": "sit",
"address.city": "amet",
"address.state": "NY",
"address.zip": "10007"
}battk
06/03/2019, 1:34 PMso you would set the values of the subrecord using values from the locationLookup
j
jackie.marler
06/03/2019, 1:34 PMtrying to wrap my head around this while being bombarded with other avatax user questions.. sorry
jackie.marler
06/03/2019, 1:35 PMis this all happening in the same client side script? or do i need to build a saved search that this is referencing?
b
battk
06/03/2019, 1:35 PM Copy code
subrecord.setFieldValue("country", locationRec.getFieldValue("country")); Copy code
subrecord.setFieldValue("country", locationLookup['address.countrycode']);battk
06/03/2019, 1:36 PMthis happens all in the client script. NetSuite will change the 3rd array parameter to nlapiLookupField into search columns
j
jackie.marler
06/03/2019, 3:40 PMi have been swamped with support calls.. thank you for all the above notes.. hoping i'll have time to test in sandbox this afternoon
jackie.marler
06/10/2019, 6:14 PMI finally had time to work on the updates, and it's all working great - thank you! I was able to set their Locations access back to View only and the client script runs just fine.
3 Views