Problem statement:

When using Search and Select mode with data or case references, you can configure default values for search fields using the Default input property. For example, if the search field is Email and you set Account.email as the default value, you might expect this value to appear at runtime when Account.email is populated through a pre-processing data transform in the flow action. However, the default value does not display at runtime in this scenario.

Default value configuration:

Runtime default value is not populated:

Why This Happens:

The system uses the property value that is committed to the database to populate the default search field. Any value set during execution (such as in pre- or post-processing data transforms) is not honored unless it is persisted before the search component renders.

Recommended approach:

To ensure default values appear in search fields:

• Commit the value into the property configured as the Default input property before the search component loads.
• You can:
  • Populate Account.email in the post-processing data transform of the previous assignment, or
  • Choose properties that already have a value stored in the database.