Written by
There was a question from the Slack community on how to set the value of the Class line. It was suggested to use SuiteFlow since it now supports the sublist fields.
I haven’t had a chance to play around it so I thought I would check it out and write the steps that I went through. Moreover, testing out if the use case would work on a workflow made me feel excited. When I was still working at NetSuite Customer Support, I had witnessed hundreds of customers requesting for this feature. So, here goes.
Note: The following steps will only make sense to you if you already have a working knowledge of workflows. This post does not aim to teach how to create workflows.
1. Create a workflow from Customization > Workflow > Workflows and deploy it on the transaction record.
2. Click on the State.
3. Click on the pencil icon to edit the state.
4. You will see a button named “New Sublist Group”. Click on it.
5. You will see this message“Note: You will be able to add actions to this group upon saving it.” Hit on Save.
6. Upon Saving, notice that “Sublist Action Group” will be created. To add actions, click on it.
7. You would want “Set Field Value” based on the said example.
8. Notice on the “Field” section, the fields are a combination of the main and line item fields. The line item fields are enclosed with the word “(Line)”.
9. Under the Value parameter, select the desired value.
10. Hit on Save.
11. Notice how the action was arranged. It displays the Action Group, the Action and its parameters. Nice! Save the workflow.
Great! Now the workflow is finished. It’s time to test it if it’s working. I deployed mine on Sales Order so I will try a test order.
And it works! See screenshot of the “Class” line item field on the test order.
To prove that it’s indeed the workflow that set it, I captured a screenshot of the Workflow History log.
There you have it. You now have an idea of what this cool feature has to offer.
However, let me give you a heads-up. This feature has some limitations. If you find any of the following particularly important to your account’s customization requirements, the best route is to file a Support case to gain visibility from the Product Management team.
- This is not yet supported for client-side triggers. This means that if you’re aiming to set a line item field when another field is selected, that wouldn’t be possible.
- This is limited to Items sublist for now. This means that this will only work to transactions with “Items” as sublist type (e.g. Sales Order, Invoice, Purchase Order, Vendor Bill, etc.). Other types of sublist like the “Expenses” sublist, “Apply” sublist of Customer Payment and Item Fulfillment or the “Line” sublist of Journal Entry are not yet supported.
- As seen from the screenshot, there are only two supported actions: Create Record and Set Field Value.
Nevertheless, I believe that this feature has a great potential, as some businesses do not have an in-house developer to write scripts for them. With having the ability to set a specific Item field without scripting, customizing the “Items sublist support” is now less complicated.
1 comment