Something like that. The Submit for Approval button workflow related to Hold is strictly a UI device for, as you mentioned, one-by-one approvals on the actual Sales Order. What I am trying to do is force the system to ignore or stop batch approvals (via Transactions -> Sales -> Approve Sales Orders) for Sales Orders where…

Having the exact same problem...7 years after this was reported. Is there a solution?

Has anyone ever solved this problem with resorting to scripting to fix this obvious defect? NetSuite swears this functionality exists through "configuration" but we have yet to find a configuration change that will make it work correctly without scripting.

I know this is a couple of years old, but I will add that the real issue with NS and Units Type is that there is no way to define valid UOM permutations for a given item. I am posting this here because I believe all of this could be coded through SuiteScript, so maybe it will be of use to someone, but it is a big…

Ridiculous that this still isn't addressed in 12 years. Many of us source products from different vendors based on quantities purchased, end customer, etc. How can there be no way to handle this on an Estimate?

The concern is about bulk fulfillment with drop ship lines since they show in the bulk fulfillment screen, even when they have not been marked as shipped. The issue is if you bulk fulfill, NetSuite fills all lines in all orders on the screen, regardless of their status of being shipped or not. This is a big problem.

Did you ever find a resolution to this problem? Our issue is similar in that we do not want to fulfill any item until it has been marked as shipped. Seems pretty standard to me, yet NS does not care if the item is marked shipped or not, it just fulfills the order anyway from Order Management - Fulfill Orders. Our situation…

Thanks, the links weren't quite what I was after, but between your help identifying the right class and the links, it led to the solution, which was actually even simpler. All that was needed was to remove "display:none" and "display:block" and replacing them with "visibilty:hidden" and "visibility:visible" along with…

Thanks, you are going down the path I was contemplating with saving the newly created records immediately, then setting fields and resaving. I was hoping to avoid that since it will be a performance and governance hit, but I don't think I have a choice at this point. As always, thanks for the help and I will write up a…

Yes, I know, that is why in the next section of code I return all dropdown list values and perform a search on both the keys and values if there was not an exact match using the 'IS' filter. The first getSelectOptions is an optimization to handle cases where there is an exact match and prevent the need to loop through the…

Here you go. I've also attached a sample of the source CSV file data.

It is deployed in our Sandbox region and it is a map/reduce script. Can you access it in our Sandbox?

Thanks! That would definitely be easiest. Is there a reference document I could have used to find those values?

Thanks. I originally had them as all lowercase like usual, but when I started running into problems, I thought maybe they needed to be in camel case since that is how they are defined in the NetSuite schema browser here: https://system.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2019_2/schema/record/account.html As…

I know this is old, but I agree with the OP 100%. The entire purpose of a special order is to order an item that is shipped to your facility prior to fulfillment. In NetSuite parlance, that is almost the entire difference between it and a drop shipment. It makes absolutely no difference if the item is an inventory or…

Thanks, I had already come to the same conclusion re: implementing a solution via workflow and custom fields as well. It is working well, but hopefully the enhancement you mention will be included soon and obviate the need for such a work-around.

Default order status is currently Pending Approval, but that does not solve the issue because when saved, the order goes into the approval queue, even if it is not ready for approval. What you describe in point 2 sounds like the correct behavior, but we do not use project records so I have no experience with those…

My goodness, I found the issue. It was due to a type where my original script was setting 'fieldid' instead of 'fieldId'. Hard to spot, but at least I know what might cause a similar issue in the future.

Thanks, the SuiteAnswer link you posted is what I am looking for and what I assumed I would have to do via SuiteFlow if the functionality did not exist. I have already setup everything as you described on our customer records. I just find it very odd that this has been a custom field/workflow solution for so long rather…

This is pretty close to what we need. Some customers require POs and some do not. I'm going to have to dig a little deeper into your reply to determine how you added a free-form text field with Case logic. I understand coding, but I'm still in the early stages of learning how to do things in NetSuite (i.e., when is…

Just a follow-up, so, am I correct I can build this using SuiteFlow? This is not traditionally what I would call a workflow, but scratching the surface of SuiteFlow, it seems like I may be able to do this very thing.

Thanks, Chris. What pitfalls led you down the path of expanding them into individual Unit Types versus Herdi's suggestion of creating a generic Unit Type (e.g., Each) with all of the various conversions contained within. It is a usability issue or something more? I also agree that it is a bit ridiculous that this table…