NexCommand AINexCom Knowledge Base
Field reference

HD Saved Reply

How to use HD Saved Reply in Helpdesk & Requests: access, working steps, fields, related records and troubleshooting.

Operations & SupportUpdated 12 October 2026Configuration-aware guidance
Open HD Saved Reply ↗Module guide

Purpose and access

Review customer and supplier requests as tickets, assign the responsible team, and record responses and resolution. Maintain the associated ERP party and document reference so support activity can be traced to the business record.

This page is a record page in Operations & Support → Helpdesk & Requests. 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: Title, Scope, Message.

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 HD Saved Reply from Operations & Support → Helpdesk & Requests, 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
TitletitleData
Required		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
ScopescopeSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Global
  • Team
  • Personal
TeamsteamsTable MultiSelect
Optional		Select the permitted linked entries; the stored rows associate those records with this document.

Linked record: HD Saved Reply Team

MessagemessageText Editor
Required		Maintain formatted content for the record; review any public-facing output before publishing.
ActionsactionsJSON
Optional · Read-only		Structured data field. Preserve the required object format and validate it before using it in an integration.

Child tables

Teams — child-row fields
FieldType / behaviorHow to use it
TeamteamLink
Optional		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: HD Team

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?