Back to this issue.... I am trying to use a restlet to create a Canadian sales order.  For Canada, tax codes are used at the item level and I need to be able to change the default tax code (selected by the tax schedule and based on the ship to province) to another that I have for that same province.  (I cannot use the default as it is different for our retail and wholesale customers).  But when I use... rec.setCurrentSublistValue({                 sublistId: 'item',                 fieldId: 'taxCode',                 value: '1444'             }); ...in the line items attached to the sales order at create in my restlet, it either is ignored or overwritten by the default tax code. I can change it manually in the sales order after creation but no matter what I have tried, I cannot get it to work in the restlet code. Last night, I thought I had a resolution by removing the pst exempt from the customer but I found that it was then using the normal tax with PST and that I still could not overwrite it in script. Strangely, I can get it to work with a SOAP call but not in a restlet. I am thinking that maybe the canadian tax province is determined on submit and that it overwrites what was set in the restlet script but that the SOAP call must do something different. Unfortunately I cannot use SOAP for this order creation. Any ideas?

your restlet is creating the record in dynamic mode, right? have you tried standard mode?

As a general rule I always use standard mode unless I must use dynamic mode. That seems to create less headache all 'round

Perhaps, save the record then once you have the IDs fire a submitfields to update the tax code on the line items, this would get a round the tax code being set on submit maybe?

I have read that submitfields does not work with sublists like the item list. For Canadian taxes, the tax code is kept on the line item

I think you are right that Submitfields will not work on sublists. What about an unscheduled scheduled script that your User event script calls thats comes along after and fixes the tax code with ignore fieldchanged set?.

I have this that runs after the SO create...

// ****************************************

        //* change tax code on line items after order create */         function changeTaxCode(SOID) {                     var Rec = record.load({                 "type": record.Type.SALES_ORDER,                 "id": SOID,                 isDynamic: false             });             var Count = Rec.getLineCount("item");                       for (var i = 0; i < Count; i++) {            Rec.setSublistValue("item", "taxcode", i, 1387);             Rec.save;     }         }

are you missing a commit ?

...and it STILL does not change the tax code.

I am not sure off the top of my head but I think so

Rec.save should be Rec.save()

I might try this is dynamic mode, 1. Record.selectLine(options) 2. Record.setCurrentSublistValue(options) 3. Record.commitLine(options)

Thanks... added that but now get... "error": {         "code": "RCRD_HAS_BEEN_CHANGED",         "message": "{\"type\":\"error.SuiteScriptError\",\"name\":\"RCRD_HAS_BEEN_CHANGED\",\"message\":\"Record has been changed\

Its because you are modify that same record in the aftersubmit event. I bet when you get that error. if you reopen the record in a new tab its actually updated correctly

You are correct that it DID in fact change the tax code... yay! Now... I currently have the record open in dynamic when I create the sales order. After so.save(), I call the function above passing the returned internal id that I then use to record.load the SO for the change. is that necessary or is the record still open after the so.save() ?

aftersubmit you cannot modify values so you wold need to load it. But that is causing the Record Changed error

So I should just try/catch my save after the standard record change and ignore that message?

try it! I dont think it will work tough.

Ignore that last... found that I had my save inside the for/next that was going through each item in the sublist to change the code... moved that and it completes without the error (and all items are updated instead of only the first)

Nice!!!