Very broad, best practices or suggestions question...
# general
j
Very broad, best practices or suggestions question here: given that NetSuite doesn't provide any kind of notes or comments field in your saved search forms and given the wide number of uses they can be put to (scripts, workflows, dynamic customer groups, views, emails, etc.) is there any best practice suggestions for capturing the specific purpose of a saved search? Or is external documentation really just the best way to go. I'm reviewing my huge list of old searches, and it's easy to spot some of the ad hoc ones and get rid of them. But I'm worried I might get rid of a search that I've forgotten was created to power a script, or workflow, for example. Just wondering what others do to prevent that.
a
Naming convention of the search is really important. If the search is used in a workflow or a script, i try to put in the search name. If the search is part of a group of searches or scripts, I try use the same prefix ID like project1
👍 1
t
Ditto on what AK47 said, naming it huge, we use a nameing concention that if it is a key search in a workflow, we add _WF at the end, if its a search used to populate a field, we put _fld at the end, if it a private user only search, the add their intials to the front of the name, if its a search used by everyone, we had the company intials to the front of the name.
🏆 1
j
I like that distinction between private and company searches -- that's a big division and important. I've been prefixing dept so far, but looking for more fine tuning. Thanks for the suggetions.
v
If I want to add a note to a saved search I add a formula (text) to the criteria with a value of 'is not ABC'. Really complex searches I'll create external documentation and just link to where that is using the same formula text thing.
j
@virtualEncoreTremor - Clever!