My Stuff
Hello Community! Josh Maxwell, a User Experience Researcher for NetSuite Foundation has fun a question for you. Imagine for a moment that NetSuite had an assistant like Alexa or Siri. What would you ask of your NetSuite assistant? Use this survey link to share your top questions to the assistant.
Here are some examples to get your creative juices flowing.
"Did I pay vendor John Doe last month?"
"Take me to my largest sales order for this month."
"What invoices haven't been paid yet?"
Here are some examples to get your creative juices flowing.
"Did I pay vendor John Doe last month?"
"Take me to my largest sales order for this month."
"What invoices haven't been paid yet?"
Comments
-
Thank you for the suggested workaround. This does work if the BOM revision is not inactive. However, if the BOM revision is marked as inactive, the code (specifically wo.save()) throws an error: "type": "error.SuiteScriptError", "name": "INVALID_FLD_VALUE", "message": "You have entered an Invalid Field Value 25 for the…
-
I understand that the behavior of that current script is expected, but my question still stands: can I somehow prevent the script from doing this? User is able to prevent this by pressing "cancel" in NetSuite UI, so can I emulate that (pressing cancel) from the script somehow (maybe passing some parameter to save)?
-
You are correct, this problem seems to be about the effective dates of the BOM revision and not about the revision being inactive. I do not observe completely identical behaviour through NetSuite UI. When I change production start date in the UI , I get the following dialog: If I press "OK", BOM revision (and component…
-
This an example of a Work Order where this is happening: Here is the BOM and available BOM revisions: I'm currently testing this with the following snippet in debugger: require(['N/record'], function(record) { var woid = 114832; var wo = record.load({ type: record.Type.WORK_ORDER, id: woid, isDynamic: false });…