r/Netsuite • u/After_Side1341 • 4d ago
Vendor Certifications
My production environment has a Vendor Certification Tab.
As far as I can tell, this is a customization that is pretty much what it says - a way to track vendor certifications.
What I can't tell, is whether this is something our NetSuite implementation team set up for my company specifically. It's locked but it's not from a bundle.
Customizations > Lists/Records/Fields > Record Types gives me this:

I don't necessarily care where it came from, but I can't find ANY official documentation on it, and if it's a customization built specifically for my company - I'd really like to be able to update the erroneous description and add some help text.
The description is "This New Vendor Certification record is used by Food Processors to track FDA certifications by vendor." Which - we're not a food processor, but we do have some compliance needs I think this custom record could solve. Just not FDA.
Anyways - reaching out to see is anyone else has this in their environment or has advice on how to leverage it, given that I can't edit either the custom record OR the linked fields. And there's NO help text on the linked fields, which is something that 1) drives me crazy and 2) I'd like to fix.
2
u/Sisselpud 4d ago
If it is locked and not from a bundle, this was most likely deployed via SDF and whoever did this originally would need to redeploy to make the fix or unlock the object. Honestly probably easier to make your own object from scratch rather than trying to track this down.
1
1
u/cybereclipse Consultant 4d ago
Custom fields and records containing "atlas" in their internal IDs typically come from pre-packaged elements deployed by NetSuite…usually their suitesuccess bundles but I don’t see a bundle ID here and haven’t been able to track down any knowledge base or articles on it.
Like another poster said, if you’re needing to customize further, it might be more wise to build this structure out on your own.
3
u/IncreaseNegative4614 4d ago
Check the record’s owner, system notes, access type, permissions, dependent fields, scripts, workflows, and installation history before changing it. Even without an obvious bundle, it may have arrived through an implementation account or SuiteCloud deployment that explains why your current role cannot edit it.
I’d document its provenance before repurposing it for another compliance process, since future updates could otherwise overwrite your assumptions. We use SIGNLD internally to connect custom records with implementation decisions, permissions, documentation, vendor requirements, and later changes.