Sets whether fields are filled out automatically with a single filter value when a new record is inserted in a table.
Values are inserted in those fields where a currently active filter expression evaluates to exactly one value. Key fields are always populated.
Differences Between the Classic Client and RoleTailored Client
If you are running the Classic client and if identical filters are set on the same field in different filter groups, then the filter value is not populated into the field when initializing a new record. For example, a filter for Document Type = Order is set on a new sales order form by the RunFormLink property, which is filtergroup 0, and also by the SourceTableView property, which is filtergroup 2. When you create a new sales order form, the filter for value "Order" is not populated into the field "Document Type," even though the two filters are simple and identical. The two identical filters are considered a complex filter, and the value is not populated into the field when a new record is initialized.
If you are running the RoleTailored client, then the behavior is different. If the following conditions apply, then the filter value is populated into a field:
Simple, identical filters are set on the same field in different filter groups.
A new record is being populated.
The filter value is assigned to the field immediately before theis executed.
For more information, see.