<@U6SNW6BC3> <@U9D2H3SBV> I set the value through ...
# suitescript
t
@mrob @ehcanadian I set the value through the UI and retrieved the value: it was the same internal ID I was trying to set. I also tried using setCurrentSublistText() - I didn't get any errors about incorrect value, but right after setting the text, I used getCurrentSublistText to retrieve the value, but it was blank. And when I tried to submit the Sales Order, I got an error telling me I needed to add an item, so I'm not sure what the issue with that is.
m
Tyler I've been having the same issue with sales order line items (clearly there are items but it says that i need one). I have a call with netsuite at 11am PDT i'll let you know if we figure it out.
e
I recall something about needing to set
fireSlavingSync
to true...
Copy code
rec.setCurrentSublistValue({
                        sublistId: "item",
                        fieldId: "item",
                        value: result.id,
                        ignoreFieldChange: false,
                        fireSlavingSync: true
                    });
could be something else I am thinking of though
m
hm... so in 2018.2 I was fine using just
setCurrentSublistvalue('item', 'fieldid', 'value')
. Do you know if there was a change in 2019.1? I have yet to find an explanation for any of the 2019.1 bugs i've encountered in the release notes lol
e
I would think it would be unlikely anything changed. This was in a client script, and if I didn't include the
fireSlavingSync
NS would complain and the item wouldn't be added
2018.1 is when I made that script
m
Okay, yeah i'm on a server script (restlet) and built it in... 2017.2? Issue just popped up for me last friday when we were moved to 2019.1
e
ah, good to know. Curious to see what the outcome of your call is