This is a really useful tip, thank you!
One NetSuite user appreciated what we’ve taught him about the best practice we featured in our previous post.
In this next article, we will be discussing some NetSuite productivity tips for you and your team.
Let’s talk about another best practice that is not usually known.
One of the most common mistakes a NetSuite account owner is guilty of is that they create Custom fields without naming the Field IDs properly.
This results in naming conflicts when bundling the fields.
Which may in turn overwrite another field, damaging your NetSuite data!
And so…. the best practice is to name your field IDs in a proper way.
How do you do it?
- What’s your company name? Come up with a three to four-letter code from there. Stark Industries? Then you can use “sti” or “strk” Innovative Online Industries (IOI)? Then use “ioi” Los Pollos Hermanos? Then you can use “lph” or “los”.
- Use that code as a prefix for the field ID. The purpose of that prefix is to promote the uniqueness of your script IDs.
- The rest of the field ID’s should be based on the field label. The reason for this is that your NetSuite Developers wouldn’t have a hard time debugging the script!
Here’s a sample Field ID:
custentity_lcc_branch_head ===> YEP! custentity12 ===> NOPE!
Doing the steps above will guarantee more efficient field management and fewer errors that will burden your transfer process in implementing solutions.
We hope you were able to find this tip in naming a NetSuite Record valuable.
In our next post, we will be discussing more of NetSuite productivity tips for you and your team.
Keep an eye out!
P.S. You might want to check our previous post on generating reports. Here’s the link: Is there a fix for Slowness of Generating Reports in NetSuite?