Best Of

I put in a case earlier and showed NetSuite the issue. They just got back to me that it's fixed. I tested it and it works.

Hi @User_KZ7N9, if you have a regular NetSuite Account and wants to upgrade to OneWorld environment, we recommend you file a Support Case for this as this is best handled by them. There's a process for this and our Support team assists in facilitating these requests.

Hope this clarifies your concern :)

Thank you again for the clarification, and apologies for the oversight. I will coordinate with the Technical Leads to assist us with this issue, as I was unable to find resources on this concern. As you mentioned, the documentation is very limited.

I will get back to you on this.

Thank you!

Hey @User_KBEB1,

Thanks for the answers.

If you only close Sales Orders when you don't want the revenue to be recognized, you can consider changing the "Create and maintain Revenue Element upon
closed Sales Order" preference to "False".

If you would like to keep the "Create and maintain Revenue Element upon
closed Sales Order" as "True", then you can create an RMA for the remaining portion of the Sales Order and close the RMA afterward.

Thank you for your insights, @Nayeem Rahman Shaik! 👏

Hi @User_4W4PN , were you able to check the comment above? :)

Hi Shamie @tech work ,

Before the role can work with any entry form for the transaction type, the role must also have permission to view or use the transaction type. So the custom role should have Edit permission level for Sales orders, in order to be able to edit the sales order form. If you decide to give the permission level on Edit for Sales order, for this custom role, you need to restrict all the other fields you don't want the role to edit. Some of them might require a script/workflow to prevent editing. I hope these details help. Best regards.

Hello, @BenjaminJ. Good day.

I have tested on my end and I can confirm that the Billing Schedule field value from the originating Sales Order of the Cash Sale cannot be exposed in the Sales by Sales Rep Summary Report.

Regarding the custom field that you have created, I will coordinate internally with our SuiteBuilder Gurus to help check why there are errors encountered when exposing it in the Report.

Hi @Glory

I've never tried the following formula on a custom field but use it in saved searches. See if it works in your case:

Formula (text) = SUBSTR({vendor}, 1, 10)

Where: {vendor} is the field you are sourcing from.

1 = instruction to start at position 1.

10 = instruction to extract 10 characters.

Using my example, this is assuming your supplier ID's are consistently 10 characters.

Yes, I submitted a case to be added to the list for the Product Feeds SuiteApp which it turns out is in early access mode. They have approved us but it is not yet implemented. I am waiting to hear back from NS Support.