moonking Green Ribbon

Thank you Ivy, you have been most helpful. You can close this ticket.

Hello Ivy, You are absolutely correct, with those settings the inventory was automatically committed and i should not have transacted Issue Components. I created a new WO and tested and I have committed inventory and can issue Work Order Completion in UI. Hopefully one last question: For Work Order Completion, looks like I…

Hello Ivy, Thanks for the quick response again! I think I will go with option 2 but I am curious about quantity commited. As you can see from setup, "Default Commit Option" is set to Available. And it shows in the WO also under "Commit". But even though there is enough quantity available, Committed columns shows 0. Why…

Thank you Ivy for a quick response. I had that in my mind so I had actually tried updating the quantity to appropriate value based on parts produced, but as soon as I leave the textbox, it changes back to 0 Not sure if this is related to 0 qty in WO in the Committed columns as shown below. Thanks again!

Thank you so much Erick, that worked.

Thank you Erick. I added as you suggested and tried below var inventorynumber=search[i].getValue('number','inventorynumber'); as well as ar inventorynumber=search[i].getValue('number'); and I still get nulls. But UI shows lot number for both columns

Solved it. For assembly item in work order make sure there is a scrap and wip account associated. Go to iten, select Accoutning tab in lower ribbon and add accounts for scrap and wip enable wip in work order

Thanks Mikko. It worked. Not sure why it didn't in the past.. but this morning I tried connecting again and magically it did! Thanks for your help.

The role has access to TBA, Rest Web Services and SuiteScripts. Is there anything else I should add? Also 2FA and SSO are disabled for this role.

@Mikko De La Fuente-Oracle I got it working thanks to a post on stackoverflow. Realm had to be in accountid_SBn. Both underscore and uppercase are important.

Mikko, this is different. Other one is TBA, this one is user credential based with integration from Domo. They use Restlets as well. Their integration steps is described here. The root cause may be the same for both.

PS: From the original title of the problem, I do see postman creates authorization key and it is appended to the header. Below is the curl with all sensitive info removed. The response is 401 "Invalid login attempt."…

Thanks for the response Mikko. We are using restlet: The login has not been successful at all, so it doesn't show up in login audit trail. Only the ones where I logged in from Web UI using login credentials show up.

Hello All, Is this fixed? As I understand from some youtube videos that we still have to do NLAuth to get authorization key. Right now if I just use oauth1.0 in postman with consumer key/secret and token key/secret it gives me invalid login error.