In other news, the ocean definitely has water.
We know. You know. Craig knows. Mass Update in NetSuite will update the records you selected, in the fields you selected, at the same time. Shocker.
But often, us NetSuite admins, just get vague emails saying
Hey team!
Can we raise the credit limits for our clinic & healthcare clients? To like 25% from 12%?And oh, Abby’s birthday is coming up. No one get her cake. Please.
Cheers,
Todd
CFOOkay. Cool. Tell NetSuite to raise credit limits for healthcare and clinic clients. Wait. How.
Ding. Another email from Todd. Ugh.
Sorry. Hospitals too.
Cheers,
Todd
CFOHelpful.
Anyyyyyway, before we touch Credit Limit, we need to know how those customers are identified in NetSuite. Mass Update will not figure that out from Todd’s subject line, and it will not wait for the third email.
Who even is a clinic
Open a customer record you already know belongs in the update. Where does it say healthcare? Category? Industry? A custom field someone added in 2019? A note that says “hospital account, ask Craig”?
Now open another one. Is it recorded in the same place?
If the account already has a field for this, start there. Check whether it means what Todd means, and whether the relevant customers actually have it filled in. A filter for Healthcare will not find the healthcare customers nobody classified. It will also not find the hospital Todd remembered in the follow-up if that record is still sitting on Clinic, or blank, or “Medical-ish” in a free-text box.
If there isn’t a suitable field, this is a good reason to create one. Agree on the choices with Todd, add it to the customer form, and classify the customers that already exist. Use a dropdown so the next person does not have to decide whether Healthcare, Health Care, and Medical-ish are three industries. Then decide who fills it in when a new customer is created.
Otherwise we will have this exact conversation again when Todd sends the next email.
A saved search is how you stop doing it from memory. If finance already has a Customer search they trust for “healthcare,” run that first. Look at the count. Look at the names. If hospitals are missing, the search is missing them, and a Mass Update copied from it will miss them too. Fix the search with Todd. Then use those filters as the Criteria on the Mass Update. Mass Update criteria is a search. A saved search you already argue about in meetings is a better template than rebuilding “clinic & healthcare & also hospitals” from an email while Abby’s birthday thread is still going.
Do not skip this and plan to uncheck extras on Preview. That Apply column only shows when the list is under 1,000. Todd’s “all of them” inside a bigger customer list is a filter problem, not a clicking problem.
This is the list you get when the filter is blank. 181 records. <Formula> in New Value. Not a list of clinics, healthcare, and hospitals. Preview, then go back. Do not Perform Update from here.
Then you can change the number
Once the set is a set, the update is the straightforward part. Lists > Mass Update > Mass Updates. General Updates → Customer. General Updates is the path that lets you put a formula on a field. The one-field shortcuts on that list will not.
Customer under General Updates. Formula lives here.
Decode Todd before you type in Formula. “To like 25% from 12%” is not a specification. If he means raise current limits by 25%, Oracle’s documented expression is {creditlimit} * 1.25. If he means set them all to the same dollar amount, that goes in Value, and Apply on Credit Limit, and there is no formula. Reply and ask. The Mass Update will do whichever one you type.
On Mass Update Fields, check Apply only on the field you mean to write. Formula is a supported SQL expression, field IDs like {creditlimit}. Set Formula will help you pick a function. It will not show you the new dollars.
Apply is on for Credit Limit. Formula is {creditlimit} * 1.25. Status is sitting on LEAD-Unqualified with Apply off.
Anything showing in Value is what gets written if you check Apply. Not “current.” If someone checks Apply on Status while scrolling, they rewrite status. For Inactive, both columns matter: Apply selects the field, Value is the on/off you intend.
Preview still will not calculate the new limits. You get <Formula>. Export Internal IDs and current credit limits first, do the math on a few rows, including $0 and blank, in sandbox if you have it. Keep that export with Todd’s email. It is a record of the original values, not a magic undo. Taking 25% off later is not a reverse of a 25% raise: $10,000 × 1.25 × 0.75 is $9,375.
Perform Update writes it. After that click, you cannot stop or cancel. Save stores the definition at Lists > Mass Update > Saved Mass Updates. Save does not raise limits. People hit Save because it is the blue button and they want to be done. Then Todd asks why the clinics are still hitting the cap.
Then Todd remembers the calendar
Hey team,
Maya’s taking over Sean’s healthcare accounts next Monday. Can you update the account owner in NetSuite?
Sean’s still handling them through Friday, so please don’t switch them yet. Just have it ready for next week.
Also, whoever ordered the cake, please see my previous email.
Cheers,
Todd
CFOWe already know how to find the healthcare customers. Now we need the ones assigned to Sean, and the change needs to wait until Monday.
For this example, we’ll use a single Sales Rep field on the customer record to identify the account owner. Confirm that this matches your setup and that the field is available for the update.
Start with the healthcare criteria we established earlier and add Sales Rep = Sean. Preview the results and compare them with the accounts approved for the handover.
On Mass Update Fields, select Apply beside Sales Rep and set Value to Maya. Check that Credit Limit and any other unrelated fields are not selected.
That defines the change. Clicking Perform Update would start it now, while Sean is still responsible for the accounts.
Todd specifically asked us to wait.
Open Schedule, enable Run Update According to Schedule, and select Single Event. Set the date for the agreed Monday, review the settings, and save the update.
Saving is what makes the enabled schedule take effect. It does not execute the update immediately. NetSuite runs scheduled Mass Updates during off-peak hours, so don’t promise Todd an exact handover time based on the date alone.
There is also one question worth settling before we leave this:
Does Todd mean the specific accounts he approved today, or whichever healthcare accounts Sean is handling when the handover happens?
If he approved a fixed list, keep the customer Internal IDs with that approval and use them to identify the intended records. Agree on how to handle accounts reassigned before Monday. Keeping Sales Rep = Sean as an additional condition would exclude an approved account if its assignment changes.
Once the scheduled run has completed, check its history and confirm that the intended customers now show Maya. Investigate any exceptions before telling Todd the handover is done.
The next time an email like this arrives, the customer classification and search criteria will already be there. You’ll still need to confirm the requested change and when it should happen, but you won’t have to work out which customers belong in the list from memory.
The cake policy is between you and Abby.
If a routine NetSuite update keeps turning into a search for missing information, we can help.
At Salora ERP, we help teams clean up customer data, build useful saved searches, and configure updates around how the business actually works. Bring us the request you’re trying to complete, and we’ll help you work through the records, rules, and setup behind it.
Todd’s email is a perfectly acceptable starting point.
sales@saloraerp.com | +1 720-254-1320 | saloraerp.com