Skip to main content
Question

Lookup-based filtering uses display value instead of key after refresh

  • April 27, 2026
  • 1 reply
  • 65 views
A
Rookie
Forum|alt.badge.img

Hello, 
I’m running into an issue with filtering a table data based on a column that has a lookup from another table. The column is an ID, but a lookup is defined to show a user-friendly string, which can have duplicate values for different ID's.

 

We use this column in a 'change filters' process action in order to display the right data. When screen is open, the data is filtered correctly based on the ID, but after refreshing the screen, filtering uses the lookup value instead of the ID as we could saw in the database event log, which leads to duplicated data. 

 

How can we make sure the filtering is based on the unique ID instead of the lookup?

 

Thank you!

      1 reply

      M
      Rookie

      Dear Alexandra,


      At the moment, process actions work slightly differently from the other filter functionality.

      In process actions, we filter using the lookup value instead of the ID, so the behavior you describe is working as intended. We plan to address this in the future, but the timeline is currently unknown.

      A possible workaround, if applicable, is to filter on another field that has unique values in the column, or to introduce a new column with only unique values that is included in the filter but hidden in e.g. grids.


      Marc Zwerver

      Terms & ConditionsAccessibility statement