OmniStudio Data Mapper Extract: FILTER LIST Output Not Rendering Unless Field Is Explicitly Mapped (Behavior Change Between v260 and v262)

Starting in version 262 (Spring '26), OmniStudio Data Mapper Extract requires that fields used in FILTER(LIST(...)) formulas be explicitly mapped in Output Mappings for each extract path that uses them.

Previously, in version 260, mapping a field for one extract path was sufficient for all extract paths using the same field to work correctly.

Version 260 behavior:

When a field (such as RecordType.Name) was mapped for one extract path, it was automatically available to other extract paths using the same field in their FILTER formulas. As a result, filtered lists worked correctly with a single output mapping row for that field.

Version 262 behavior:

Each extract path now operates independently. If a field is used in a FILTER formula for a particular extract path, that field must have its own explicit output mapping row for that specific extract path. Without it, the filtered list may return empty results or may not appear in the output.

As a result, if a Data Mapper Extract uses FILTER(LIST(...)) formulas across multiple extract paths and the filtering field is mapped only for one of those paths, the other paths may stop producing results after upgrading to version 262.

Example:

If there are two extract paths, AccountList1 and AccountList2, both filtering by RecordType.Name, and only AccountList1:RecordType.Name is included in Output Mappings, then AccountList2 will return empty results in version 262.