PopulationMethod

Overwrites the values of the target fields with the results from the lookup, regardless of whether they are currently empty or already populated.

When to Use

• When the lookup source is authoritative and should always set the field values.
• For scenarios where you want to ensure the most current or accurate data is always present.

Example Scenario

• After a successful lookup, the "Customer Name" and "Address" fields are always updated with the latest values from the external system, even if they were previously filled.

> Tip: Use with caution if you want to preserve user-entered or previously extracted data.

Only sets the value of a target field if it is currently blank. Existing values are preserved and will not be overwritten by the lookup.

When to Use

• When you want to supplement missing data without replacing user-entered or previously populated values.
• For initial data population, onboarding, or import scenarios where some fields may already be set.

Example Scenario

• If the "Product Description" field is empty, the lookup fills it in; if it already contains a value, the lookup leaves it unchanged.

The lookup will not update any target fields. Use this mode for validation-only scenarios, where you want to check values against an external source but not change them.

When to Use

• When the lookup is used solely to validate existing data, not to populate or update fields.
• For compliance or audit scenarios where data must be checked but not altered.

Example Scenario

• The lookup verifies that the entered "Account Number" exists in the external system, but does not update any fields with returned data.

> Tip: Use this method to enforce data integrity without modifying user or extracted values.