プロフィール
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
コメント
-
I wasn't asking if you are able to set promotions via script. Is it auto-applying the promotion via script?
-
Can you confirm if it is not supported server side? If it is a bug I don't want to look up every promotion.
-
I tried a simple script. Also tried a simple csv. Neither worked. I can see the promotion in the promotions tab but it says not applied. In the ui it applies. require(["N/record"], function (record) { var activeRecord = record.create({ type: "salesorder", isDynamic: true, defaultValues: { entity: 13121 } });…
-
Does this mean it is not supported server side ie CSV, web services? What makes suitelets special that it doesn't work there? These promotions are configured to auto-apply.
-
You can disregard, apparently there was a script controlling the Non-Taxable for some reason. When I turned it off it started sourcing the Tax Group variant correctly.
-
I was able to fix it myself by changing the order of the sourcing fields. Not sure why but it resolved the issue.
-
I still haven't received any response from partner support. Can you please close that case? I will file it under the customer's account.
-
Can you provide my case number? I didn't receive a notification nor does the ticket show in my case list.
-
The browser's Document Object Model, i.e. get the button element in JavaScript and click it through JavaScript.
-
I believe the only way to do what you are describing is to use the DOM and get the button element and click it. I'm not sure if a client side workflow action script will do it but I know it will work with a client script. In either case it will require a script to click the button without user interaction,
-
If you add it to the header macro instead of the body it will automatically show up on every page.
-
I never got it to work and I didn't have time to waste. I think the product needs to mature a little bit. I ended up using exceljs and it worked without issues even though it is slightly older.
-
I tried to follow the sample in the XLSX documentation for NetSuite but it didn't work for me. I then tried switching to node but it kept hanging. I ended up switching to a different library.
-
Pretty sure I was able to do this to add conditions. It's been a few years since moving to advanced pdfs but used to do it regularly.
-
If you don't have an existing workflow already for the purchase order approval the standard one by NetSuite can be installed via bundle 239645.
-
I wouldn't recommend modifying the workflow as that can be a slippery slope although if you are proficient with workflows then it should be fine. Alternatively I would create a second workflow and add your logic there. For the use case you describe you can use the Set Display Type to DISABLED when the User != Next Approver
-
That's a bit tricky. I wonder if adding a condition will do the trick to_char({shipdate},'D') is 2 then adjust the formula accordingly.
-
If you use advanced pdfs and know a little bit about templates you can try the following snippet (although likely requires some tweaking/formatting): <td colspan="4" align="left"> <!--This parses the hidden field that contains the serial numbers--> <#if tranline.inventorydetail?has_content> <#list…
-
Is that a new item fulfillment or an existing one? It will only default on new item fulfillments on a go forward basis.
-
Not that I'm aware in the native package tracking number sublist field using out of the box workflow functionality. In a workflow you would have to write a workflow action script to manipulate the package sublist or alternatively a non-workflow user event script.
-
I don't believe it is currently possible to enter an inventory adjustment with Posting = F. You can upvote the enhancement #112294 Require approval before an inventory adjustment affects the company records or books.
-
Do you mean a saved search PDF result? If so you can modify and customize the PDF by selecting New Template when editing the saved search: It does require a little bit of knowledge with HTML and working with NetSuite templates.
-
Thanks that makes sense. Not sure what happened but when I first created the item it allowed me to check out with the parent but I edited and saved the record and then it started asking for the option.
-
I'm not sure if an event fires so not sure you can listen to it. It's possible that it does but I would doubt it. Instead you would have to run a scheduled process on the filter cleared = T and then maybe add a custom field to indicate it has been processed.
-
I don't believe any scripts can read the bank statement data currently as it is not supported via scripting. One possible work around but I haven't tested or even checked if it would work would be to read the Cleared and Cleared Date field of the customer payment record and use that to set the payment date. What I'm unsure…
-
I don't believe there is a native memo field on the vendor record, only a comments field that allows a user to enter some comments about the vendor. If you see a memo field on the vendor it is either a custom fields or a field that has been relabeled. Natively NetSuite doesn't source the memo from the vendor but it is a…
-
Unfortunately there are a handful of fields in NetSuite that are not present when customizing forms with 3rd party billing being in that category. I believe the only way would be to hide them in a before load workflow.
-
It is not possible to add a custom field to the packaging sublist. One workaround would be to add a field via a before load script to the sublist and store the data submitted in another field. Then you can render the data back to the sublist when populated. Keep in mind the impact of this approach on reporting if you need…
-
That is unusual as we have a similar process to bill time entries and I know it can result in an error when it is invoiced however removing it from the invoice usually clears it up for us. Is it possible it ended up on another invoice?
-
I think the bundle number is 240841 but this was when it was installed over a year ago.