Skip to main content
Question

Filtering values of a custom lookup field (non-system lookup)

  • December 12, 2025
  • 4 replies
  • 27 views

Hello,

Is it possible to filter the available options of a custom lookup field when the lookup list is custom-defined.

Specifically, I would like to know whether custom lookup lists support any kind of filtering logic, or if filtering is only supported when the lookup source is a system table.

If this is not supported, is there an officially recommended approach for handling conditional options in custom lookup fields?

Thanks.

4 replies

Forum|alt.badge.img+13

Hello MANAF,
 

Have you checked the following page in our documentation, which shows the availability and scope of expressions for the different types of fields:

Expressions and Filters in assyst - assyst25R2Wiki

A Lookup Filter Expression can be applied to Single Select Lookup and Multi Select Lookup fields (System or Custom fields).

Within a Lookup Filter Expression, you can refer to a Single Select Lookup (system or custom field).

I hope this helps.
 

Best regards,

Caroline


Hello MANAF,
 

Have you checked the following page in our documentatio), which shows the availability and scope of expressions for the different types of fields:

Expressions and Filters in assyst - assyst25R2Wiki

A Lookup Filter Expression can be applied to Single Select Lookup and Multi Select Lookup fields (System or Custom fields).

Within a Lookup Filter Expression, you can refer to a Single Select Lookup (system or custom field).

I hope this helps.
 

Best regards,

Caroline

Hello Caroline,

Thank you for your reply.

I would like to clarify my requirement more clearly.

I have a custom single-select lookup field that contains specific options (for example: Load Balancer, WiFi, Create Server).
What I need is to control which options inside this lookup list are visible, based on the type of the Affected User.

  • If the affected user is a technician (not a Contact User), all options in the list should be visible.

  • If the affected user is a Contact User, only one option inside the list (for example WiFi) should be visible, and the other options should be hidden.

The lookup field itself should always be visible; only the options within the list should change.

Could you please confirm if filtering individual options within a custom lookup is supported, and what the recommended approach would be?

Best regards,
Manaf


Forum|alt.badge.img+13

Hi Manaf,

Could you clarify your scenario : If the affected user is a technician not a Contact User, or a Contact User???
Affected user is a contact user in assyst. What is the criteria you are using here? You need to have an option, a setting on the Contact User form to base your filter on.

Few examples are available on the documentation : Creating Lookup Filters for System Fields - assyst25R2Wiki

Best Regards,


  • Author
  • December 15, 2025

Hi Manaf,

Could you clarify your scenario : If the affected user is a technician not a Contact User, or a Contact User???
Affected user is a contact user in assyst. What is the criteria you are using here? You need to have an option, a setting on the Contact User form to base your filter on.

Few examples are available on the documentation : Creating Lookup Filters for System Fields - assyst25R2Wiki

Best Regards,

Hello Caroline,

Thank you for your response.

Let me clarify my requirement more precisely, as it is related to SVD and the Alias of the Affected User.

I have a custom single-select lookup field that contains several predefined options.
What I need is to show or hide specific options inside this custom lookup based on the SVD assigned to the Alias of the Affected User.

More specifically:

  • If the Affected User’s Alias is associated with a technician SVD, the custom lookup should display all available options.

  • If the Affected User’s Alias is associated with a Contact User SVD, the custom lookup should display only specific options, while the remaining options should be hidden.

The lookup field itself should always be visible; only the options within the custom lookup list should be filtered based on the SVD of the Alias linked to the Affected User.

Could you please confirm whether this type of value-level filtering on a custom lookup based on Alias/SVD is supported in assyst, and what the recommended approach would be?

Best regards,
Manaf