New AI Description Field on Custom Records, Fields, and Transactions

What changed

A new AI Description field (max 250 characters) now appears in the main body section of definition pages for:

• Custom Records
• Custom Fields
• Custom Transactions

NetSuite AI features consume this field to understand the semantic purpose of each custom object. The primary consumer today is the NetSuite AI Connector Service, which exposes NetSuite data to external AI platforms (e.g., ChatGPT, Claude) via Model Context Protocol (MCP). When an external model queries your account through MCP, the AI Description is used to resolve which custom objects are relevant to a given prompt.

The field is informational metadata only — it does not affect record behavior, scripting, workflows, or saved searches. It is not exposed through SuiteScript N/record field reads in the current release notes, though Oracle does not clarify whether it is scriptable. Expect it to behave like other definition-level metadata fields (similar to the existing Description and Help fields on custom object pages).

What to do

1. Audit your custom objects. Identify high-value custom records, fields, and transaction types — especially those that external integrations or AI assistants need to reason about. Populate the AI Description with a concise, unambiguous explanation of each object's business purpose.
2. Write for machines, not marketing. The 250-character limit is tight. Focus on what the object stores or represents and how it relates to standard NetSuite entities. Example: Stores vendor rebate tier thresholds linked to Item records via custrecord_rebate_item.
3. Coordinate with MCP rollout. If you are evaluating or already using the NetSuite AI Connector Service, populating these descriptions is a prerequisite for useful AI responses. Without them, external models will only see internal IDs and field labels, which are often cryptic.
4. Check scriptability. Oracle's notes do not confirm whether the AI Description field is readable or writable via SuiteScript (N/record) or REST/SOAP web services. If you need to bulk-populate descriptions programmatically, test access via record.load() on a custom record definition or check the Records Catalog for the field's internal ID before writing a migration script.

Limitations and unknowns

• Oracle does not document the internal field ID for the AI Description field. Inspect the DOM or Records Catalog to confirm.
• No mention of CSV import support for bulk-populating descriptions.
• No indication whether this field is included in SDF (SuiteCloud Development Framework) custom object XML, which matters for sandbox-to-production deployment.