3761438 - user custom column search defaults to startswith instead of contains after 1h2026 despite matchoptiondefaults[op_contains]=true; standard columns unaffected

Post 1H2026 release user custom column search operator does not adhere to search configuration file of matchOptionDefaults[OP_CONTAINS]=true and instead defaults to StartsWith whereas standard user columns still adhere to this setting.

SAP SuccessFactors Learning

1. Navigate to System Administration > Configuration > Search.
2. In the Search configuration, ensure the following entries exist:

• matchOptionDefaults[OP_STARTWITH]=true
• matchOptionDefaults[OP_GREATER]=true
• matchOptionDefaults[OP_CONTAINS]=true

1. Open User Search and add any custom column as a search criterion.
2. Observe that the default operator for the custom column is StartsWith instead of Contains.
3. Compare with standard user columns in the same User Search and observe they default to Contains as expected.

The cause of this issue is currently under investigation. Please follow this KBA for updates.

The solution of this issue is currently under investigation. Please follow this KBA for updates.

custom, column, user, search, operator, matchOptionDefaults, OP_CONTAINS, OP_STARTWITH, contains, startswith, 1H2026, configuration, selector, default, operator, criteria.CustomColumn, lms, change, learning, KI1H2026 , KBA , LOD-SF-LMS-ADM , System Admin, Global Variables, References , Bug Filed