Customizing Product Fields

Fields in products 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 product, the form displays only the fields included in the create form in the fields setup. After you save the product, the details page displays all the fields, including those hidden during creation, so you can review or update them later. To include fields in the create form,

1. Go to Setup > Configure, Price, Quote (CPQ) > Products from the left sidebar.
2. Under Form settings, click Edit.
3. Check the Show in create form checkbox.

5. Click this icon to save your changes.

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 fields mandatory,

1. Go to Setup > Configure, Price, Quote (CPQ) > Products from the left sidebar.
2. Under Form settings, click Edit.
3. Check Show in create form and Make this field required.

5. Click this icon to save your changes.

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

In the create form and in the details page of the product, 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.

API name

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

Field type

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

Description

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

Instructions

To provide specific directions or format requirements to guide users in entering information correctly and avoiding errors. This appears 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 product name.”

Options

Provides the list of options users can select from when entering data in the field. These options apply only to 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 product record.
• Make this field required - Check this option to make the field mandatory when creating a product record.
• 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).
• Make this field non-editable on details page - Prevents users from editing the field after creation. (This can be done from the field’s details page alone and not from the listing page)

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.

Dependency between selling type and related fields

The Selling type field includes two system-defined options: Standalone and Subscription.

When the selling type is subscription

It is mapped to several fields with system-defined behaviors:

• Mapped to Subscription type with options Term‑based and Evergreen.
• When Term‑based is selected, it is mapped to the Term field and the field becomes mandatory.
• When Evergreen is selected, the Term field is not applicable.
• Mapped to Charge type, which defaults to Recurring and is mandatory.
• The Recurring charge type is mapped to the Billing frequency field with the options Monthly, Quarterly, Half yearly, and Yearly, and this field is mandatory.

When the selling type is standalone

• Mapped to Charge type, which defaults to One‑time and is mandatory.
• The Subscription type, Term, and Billing frequency fields are not applicable.

All these mappings and option values are system‑defined and cannot be changed.