Naming NetSuite Field IDs

This is a really useful tip, thank you!

That was what a NetSuite user said when I taught him about that best practice that I featured from my last post.

In my next post, I will be discussing some NetSuite productivity tips for you and your team.etSuite record.

This time, let's talk about another best practice that is not usually known.

One of the most common mistakes I find NetSuite account owners to be 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?

1. 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" 2. Use that code as a prefix for the field ID. The purpose of that prefix is to promote the uniqueness of your script IDs.

3. 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:

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.

I hope you were able to find the tips above valuable.

In my next post, I will be discussing some NetSuite productivity tips for you and your team.