Customizing Sales Document Fields

Fields in sales documents can be customized to improve usability and ensure they align with your sales process. While you cannot change their field type after creation, you can modify aspects such as visibility, mandatory status, dynamic behavior, and field order at any time. In addition, system fields cannot be deleted.

Field visibility

When creating a sales document, the form displays only the fields included in the create form in the fields setup. To include a field in the create form:

1. Navigate to Setup > Configure, Price, Quote (CPQ) > Sales Documents.
2. Select the document type and open its tab.
3. Locate the field(s) you want to include in the creation form.
4. In the Form settings column, click
5. Check the Show in create form option.
6. Click

Alternatively, you can check the Show in create form option in the field details page, which you can access by clicking the field name in the field listing page.

Required fields

To make a field mandatory,

1. Go to Setup > Configure, Price, Quote (CPQ) > Sales Documents.
2. Select the document type and open its tab.
3. Locate the field you want to make mandatory.
4. Under Form settings column, click .
5. Check Show in create form and Make this field required.
6. Click

Alternatively, you can check the Make this field required option in the field detail page, which you can access by clicking the field name in the fields listing page. Note that Show in create form must be checked before that.

Field order

When creating a sales document, fields appear in the order you set using the Reorder fields option on the fields listing page’s toolbar.

Field name

The label shown to users wherever this field is used. It can be edited to make it clear and descriptive.

Display name

The display name is applicable only to the Pipelines and Sales Documents modules, where field reuse is available.

During field reuse, the display name lets you change how the field label appears for each individual pipeline or sales document, while the underlying field remains the same. This helps tailor the label to the specific context without creating duplicate fields.

API name

This name is used to reference the field in the API and other integrations. It cannot be changed after field creation.

Field type

The data type (e.g., Single-line text, Multi-line text) of the field. This determines how the field behaves and what data it can store. It cannot be changed after field creation.

Description

To provide a brief explanation or context for this field. This helps users understand the purpose or importance of the field. This description can either be shown below the label or as a tooltip based on whether Display description as tooltip option is checked or not.

Instructions

To provide specific directions or format requirements to guide users in entering information correctly and avoiding errors. This will be displayed below the input field. Example: “Enter the date in DD/MM/YYYY format.”

Placeholder text

To provide a short hint about what to enter. This text appears inside the field until the user starts typing. Example: “Enter contact name.”

Options

Provides the list of options users can select from when entering data in the field. These options are applicable only for fields with selective field types, such as Single-select dropdown, Radio button, and Checkbox list fields.

Field display and editing configurations

• Show in create form – Check this option to display the field when creating a sales document.
• Make this field required – Check this option to make the field mandatory when creating a sales document.
• Conditional logic – Allows you to set rules that determine the behavior of the field based on values from other fields. Configure conditions to dynamically display this field as optional or mandatory when filling in the document fields before sending a document. For more details, visit: Understanding conditional logic in fields
• Controlling field (Field dependency) – Allows you to add a master field that controls the behavior of the field, turning it into a dependent field. This dependency allows for configuring the dependent field’s state (visible, required when visible) or the automatic population of values based on the controlling field’s inputs. For more details, visit: Understanding controlling fields (Field dependency)

If a field is included in the create form, you cannot add a controlling field or apply conditional logic to it. Similarly, if a field is already dependent on a controlling field or displayed based on conditional logic, it cannot be directly included in the create form.