---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Use case: Configure dynamic formatting for the adjustment value field

# Configure dynamic formatting for the adjustment value field {#ariaid-title1}

Release version: Brazil  
Updated September 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure the transaction layout so that the adjustment value field displays as a currency amount or a percentage, based on the selected adjustment type.

## Before you begin

Role required: admin

You need administrator access to transaction layouts in productized pricing.

## About this task

The following table describes the properties of the dynamic format type, which sets a field's display format based on the value of another field.{#configure_dynamic_formatting_price_adjustments__table_xkq_nmj_clc__entry__2}

| Property | Description |
|-|-|
| `type` | Set to `dynamic`. |
| `controller` | The variable name of the field whose value determines the format of the target field. |
| `rules` | An ordered array of rules. Each rule has a `format` and a `values` array. |
| `format` (in a rule) | The format to apply when the rule matches. It uses the same schema as the outer format. You can't nest a `dynamic` format inside a rule. |
| `values` (in a rule) | The underlying values of the controller field for which the rule applies. Use the underlying values, not the display labels. |
[Table 1. Dynamic format properties]

{#configure_dynamic_formatting_price_adjustments__table_xkq_nmj_clc}

## Procedure

1. Navigate to CPQ AdministrationTransactionLayouts.
2. Open the layout that contains the manual adjustment fields.
3. Switch to the YAML editor.  
   The visual editor doesn't support this change.
4. Find the discount adjustment value field (`txn.line.pricing.discount.value`).  
   Keep `type` as `FormattedNumber`. Change only the `format` property. The adjustment type field (`txn.line.pricing.discount.adjustmentType`) must be a `Picklist` in the same layout. The discount reason field (`txn.line.pricing.discount.description`) is optional.
5. Replace the fixed `format` with a dynamic format that uses the adjustment type field as the controller.  

       format:
         type: dynamic
         controller: txn.line.pricing.discount.adjustmentType
         rules:
           - format:
               type: currency
             values: [MARKDOWN_AMT, PRICE_OVERRIDE]
           - format:
               type: unit
               unit: percent
             values: [MARKDOWN_PER]

   In `values`, use the underlying values of the adjustment type field, not the display labels. Rules are evaluated in order, and the first matching rule applies. Don't use `type: percent` for `MARKDOWN_PER`, because it doesn't match how the adjustment is sent to pricing.
6. Save the layout, then deploy it.
7. Reload the transaction and check the display for each adjustment type.

## Verification results

{#configure_dynamic_formatting_price_adjustments__entry__16}

| Adjustment type | Value entered | Adjustment value display | Net price after reprice |
|-|-|-|-|
| MARKDOWN_PER | 10 | 10% | $45 (−$5) |
| MARKDOWN_AMT | 10 | $10 | $40 (−$10) |
| PRICE_OVERRIDE | 10 | $10 | $10 (−$40) |
[ ]

*[\>]: and then


