Preventing Duplicate Users in sn-record-picker Using Reference Qualifiers - Support and Troubleshooting

Preventing Duplicate Users in sn-record-picker Using Reference Qualifiers Issue When using the sn-record-picker element, users appear multiple times in the dropdown list. This occurs because the underlying table ( u_m2m_customer_account_sys_user ) includes multiple entries for the same user associated with different partners, resulting in duplicate display.

Symptoms Duplicate user records in the record picker list

Release All releases

Cause The sn-record-picker references a many-to-many (M2M) relationship table, which stores multiple records for the same user when linked to different customer accounts or partners. This causes users to appear more than once in the selection list.

Resolution Using Reference Qualifiers To prevent duplicate users in the sn-record-picker , use reference qualifiers to filter the list based on specific criteria.

Option 1: Simple Reference Qualifier (Filter by Customer/Partner) If your users are linked to a customer account, use a dynamic filter:

account=javascript:gs.getUser().getCompanyID() Or use a reference field:

account=$[current.account] Option 2: Advanced Scripted Reference Qualifier Use a scripted reference qualifier to fetch only unique users based on logic from a related table (e.g., M2M):

Example (on a reference field to sys_user):

var users = []; var m2m = new GlideRecord('u_m2m_customer_account_sys_user'); m2m.addQuery('u_customer_account', current.u_customer_account); // Or your related field m2m.query(); while (m2m.next()) { if (!users.includes(m2m.u_user.toString())) { users.push(m2m.u_user.toString()); } } answer = 'sys_idIN' + users.join(','); 💡 This ensures the sn-record-picker only shows each user once, even if they are linked to multiple partners.

When to Use Reference Qualifiers Use reference qualifiers when configuring fields on forms, tables, or widgets that need to pull unique, relevant records.

Always point to the base table ( sys_user ) and use the qualifier to filter by related data, rather than querying the M2M directly.