setValue() on fields in the shippingaddress subrec...
# suitescriptc
Craig
03/31/2022, 9:05 PMsetValue() on fields in the shippingaddress subrecord (on an SO) should save when the SO saves right? I'm setting the fields in beforeSubmit but the saved transaction isn't showing the fields I've set.
b
battk
03/31/2022, 9:06 PMis the
shipaddressbattk
03/31/2022, 9:07 PMor are the actual fields on the subrecord not being set
c
Craig
03/31/2022, 9:07 PMThe latter
Craig
03/31/2022, 9:07 PMin regards to the former, I'm not interacting with the shipaddress field.
b
battk
03/31/2022, 9:08 PMare you using the
shipaddressbattk
03/31/2022, 9:08 PMor are you actually examining the actual address subrecord
c
Craig
03/31/2022, 9:08 PMYes, that's the field I'm using to visually confirm
b
battk
03/31/2022, 9:09 PMedit the sales order in the ui and edit the address to see the actual address subrecord to confirm
c
Craig
03/31/2022, 9:16 PMAfter some poking around I can see the addresses I've been setting have all been saved but the shipaddress field is not set to the saved address
Craig
03/31/2022, 9:17 PMand the fields are being correctly set and saved on the subrecord
b
battk
03/31/2022, 9:18 PMextra common for the address fields to not source correctly
battk
03/31/2022, 9:19 PMthe sure fix is to set the
shipaddressbattk
03/31/2022, 9:20 PMthe exotic fix is to use Record.removeSubrecord first
c
Craig
03/31/2022, 10:04 PM@battk it looks like this one line of code fixed the issue:
Copy code
soRecord.setValue({fieldId: 'shipaddresslist', value: ''});Craig
03/31/2022, 10:04 PMthe shipaddress now shows the values I set in the subrecord.
Craig
03/31/2022, 10:05 PMI got that from a SuiteAnswer - I don't know why that works, I think it forces the address to be added as 'custom' instead of 'new'.
Craig
03/31/2022, 10:06 PMtypical NS, very obscure fix/workaround that you only find out by luck.
27 Views