NexCommand AINexCom Knowledge Base
Field reference

DocType Layout

How to use DocType Layout in Customization: access, working steps, fields, related records and troubleshooting.

System AdminUpdated 12 October 2026Configuration-aware guidance
Open DocType Layout ↗Module guide

Purpose and access

Use Customize Form and Custom Field for supported record extensions. Choose an appropriate field type, label, identifier and placement. Test required, unique and link behavior in staging, and check impact on reports, imports and APIs.

This page is a record page in System Admin → Customization. Use the link above to open the configured destination; permissions are checked by the destination service.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Before you start

Prepare the required information: Document Type, Route, Fields.

Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.

Working steps

  1. Open DocType Layout from System Admin → Customization, or use ERP Search.
  2. Filter the list and open the relevant record. To add a record, use Add/New when your role provides that action.
  3. Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
  4. Add the required child rows. Review each row’s identifiers, linked records and values, using the child-table field reference below.
  5. Save the record and address validation messages. Reload and verify the saved values and relationships.
  6. Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.

Field reference

These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.

FieldType / behaviorHow to use it
Document Typedocument_typeLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: DocType

RouterouteData
Required		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
FieldsfieldsTable
Required		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: DocType Layout Field

Client Scriptclient_scriptCode
Optional		Administrator/integration field. Use a validated configuration or supported script and test its impact before deployment.

Child tables

Fields — child-row fields
FieldType / behaviorHow to use it
LabellabelData
Optional		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
FieldnamefieldnameSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.

Troubleshooting

  • Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
  • Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
  • Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
  • Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.
Was this useful?