How to Create a Custom Record Type in NetSuite

Create and configure a custom record type

1. 1Go to Customization > Lists, Records, & Fields > Record Types > New. Enter Name; the ID defaults to _name and the full script ID becomes customrecord_name. Set the ID deliberately now, because it is what scripts and SDF reference.
2. 2Choose Access Type: Require Custom Record Entries Permission (recommended), Use Permission List, or No Permission Required. Most production records should use the entries permission so roles are granted per record type.
3. 3Tick the options you need: Include Name Field, Allow Quick Add, Show ID, Allow Attachments, Allow Inline Editing, Include in Global Search, Enable Mail Merge, and Show in List.
4. 4Save, then open the Fields subtab and add custom fields (free-form text, list/record, currency, checkbox, date). A list/record field pointing at Customer, Item or another custom record is how you build relationships.
5. 5For a parent-child structure, create a field on the child record of type List/Record that points to the parent type and tick Record Is Parent on the child field. The child then appears as a sublist on the parent form.
6. 6On the Permissions subtab, grant each role a level (View, Create, Edit, Full). On the Forms subtab, customize the entry form and set the preferred form.
7. 7Create a record entry from the list under Lists > Custom or the menu you assigned, then build a saved search of type Custom Record to report on it.

Parent-child records and sublists

// SuiteScript 2.x: create a custom record entry
record.create({ type: 'customrecord_equipment', isDynamic: true })
  .setValue({ fieldId: 'name', value: 'CNC-04' })
  .setValue({ fieldId: 'custrecord_eq_location', value: 3 })
  .save();

-- SuiteQL against a custom record table
SELECT id, name, custrecord_eq_location
FROM customrecord_equipment
WHERE isinactive = 'F'

Common pitfalls

• !Leaving the default script ID: scripts and SDF then depend on a name someone later wants to change, and IDs are painful to alter after data exists.
• !Using No Permission Required, which exposes the record to every role that can reach the URL or a saved search.
• !Forgetting to grant the custom record permission to integration roles, so a RESTlet or SuiteTalk call returns a permission error while the UI works for admins.
• !Building a custom record for a simple drop-down. A Custom List or Custom Segment is cheaper to maintain.
• !Adding hundreds of fields to one type, which slows forms and searches. Split into related records.