This is something new to me, thanks for sharing the article @MikeBucklaew! Anybody knows what are those 'indexed fields'? Based on my test, "Name", "Email" and "City" are included in that list. Lea Celosa Columna Independent NetSuite Technical Consultant leacc.cloud https://www.linkedin.com/in/leacc/

I am not sure if point and click customization supports this but if you are familiar with User Event scripts (Before Load), you may give it a shot.

pcutler listed them down perfectly. After submit scripts should be sparingly used when it comes to same record processing. If it's the same record you're simply updating, better use before submit scripts. Not only does it result into errors like the one you mentioned, it also heavily affects performance of the record…

I'm calling setSublistValue in a beforeLoad method, and while the value is changing, the text is not updating. Is there anyway I can force it to update? slavingSync doesn't seem to be applicable in setSublistValue, and since I am in a beforeLoad, I cannot use currentRecord. Can you share your code please?

The user event script must execute and trigger the MR. Are you sure that no other changes were made aside from moving the logic from before submit to after submit?

I am not sure if it's indeed related to the search being run by a different user. "SSS_AUTHOR_MUST_BE_EMPLOYEE" is associated with the the email.send API where the author set by the script is not a valid NetSuite employee. Are you sure the right parameters for this API are set in the script? leacc.cloud

Tried this snippet on my end and it works fine. Are you sure that it's the line that is causing the error? Can you try commenting out other lines or simplifying your script? require(['N/record'], function(record) { var currentRecord = record.load({ type : 'vendorbill', id : 10 }) var newLineId =…

karenn what's the urgency level of the defect ?

"An unexpected SuiteScript error has occurred" errors do not always mean it's a script that is causing the error. Sometimes it's also caused by a custom field or a workflow containing an invalid formula. Try going through your custom transaction body fields or workflows and see which one of them contain funky…

This is my first time to hear such record type. Are you sure this is not a custom record in the system? How are you navigating to that record? How does the URL look like when you are opening that record?

Hi, I've recently just discovered SuiteScript and can see that there are so many functions and capabilities to it. Curious to know as to how people are using SuiteScript that benefits them the most? Thanks in advance! What I've learned over the years is that "not because SuiteScript can, you should". SuiteScript is only…

What I would add is when you are debugging, ensure that you're processing one record only. You can do this by: 1) Setting an internal ID on the getInput stage or 2) If you're using a saved search, add a filter on your where Internal ID (Number) is <this number>

Good to know it was fixed then. :)

Yes, the syntax is correct. You just have to make sure that you're referencing the right internal id of the custom form.

khultquist unfortunately this is not possible via standard mass update or workflows. If you're familiar with scripting, you can use record.detach as shown on the snippet below: var rec = record.detach({ record: { type: 'contact', id:'12' }, from: { type: 'customer', id:'11' } })

In case you're still looking for the snippet for ad-hoc search: require(['N/search'], function(search) { var documentSearch = search.create({ type: 'file', 'columns': ['name'], filters: ['folder', 'anyof', null, 78239] }); var results = documentSearch.run().getRange({ start: 0, end: 10 });…

You cannot modify the NetSuite generated GL Impact. You can explore Custom GL if that can achieve your business requirements.

Contacts are not a subrecord. Subrecords are those that cannot exist independently without a parent record, which is not the case for Contacts. You can create contacts even without a parent transaction/opportunity record. The "Relationships" tab you see on the Opportunity record is more of a Related Records type. This is…

This can be accomplished by passing into getValue(columns[n]) a reference to the search column whose value you would like to retreive. https://system.netsuite.com/app/help/helpcenter.nl?fid=section_46988464355.html This is also my favorite way of retrieving search result values when there are tons of multiple columns in my…

You would have to come up with a search that will have joined fields (Contacts..). On your script you will check if the search results are more than or equal to one. You can start off by creating a saved search in the UI, use internal ID as the filter and use the Contacts joined fields on the Results tab. From there you…

By default fireSlavingSync is set to false. By slaving it means that "other fields (child fields) are changing its value based on what you set on that parent field". One great example is the 'Item' field on the 'item' sublist. When you set the 'item' field, other fields are sourcing its value from it. (e.g. description,…

ashgupta1489, can you please check first if you can set the "Account" field in the UI? (Transactions > Payables > Pay Single Vendor) For you to apply a payment to an item, ensure that you're manipulating the 'apply' sublist.

Hi Laaki, this is only possible if the account you are testing with have multiple queues. Multiple queues are obtained by purchasing a SuiteCloud Plus license.

I do wish for a wider record/field exposure list in SuiteScript 2.0. I had an issue with SS 2.0 where I wrote a script to update Deposit records, only to find out that it's not supported! Had to revert back to SuiteScript 1.0. :h_a_w::h_a_w::h_a_w: Oh, and NS also heard me! Read in the Release Notes that it's going to be…

I do wish for a wider record/field exposure list in SuiteScript 2.0. I had an issue with SS 2.0 where I wrote a script to update Deposit records, only to find out that it's not supported! Had to revert back to SuiteScript 1.0. :h_a_w::h_a_w::h_a_w:

I hope my article can help someone who comes across the similar problem. https://leacc.cloud/2018/09/03/suitescript-error-you-have-entered-an-invalid-field-value-8-20-2018-for-the-following-field-trandate/

Exporting CSV from search results via script is now made hassle free through N/task.SearchTask. Please check out my blog post if you'd like to know more details: https://leacc.cloud/2018/08/23/suitescript-2-0-why-you-should-check-out-n-task-searchtask/

Without scripts, I don't think there's a way for you to do it in workflows. You may want to request this as an enhancement to Support.

Upon checking I only see two possible Tax code fields when adding a sublist action in workflows: Tax (Line) and Tax Item. Tax(Line) is a checkbox field which is not what you need and seems that Tax Item is the tax field on the header level. What I would suggest you to do is report this to NetSuite Support as it's a…

Yes, that's true. This is currently limited to "Items" sublist and server triggers. Any use case outside from that will have through the SuiteScript approach. leacc.cloud