Skip to main content
Solved

What controls the order of a lookup reference in the filter form?

  • November 12, 2025
  • 4 replies
  • 21 views

When I set a lookup reference to “Visible for filter” = “Always”, it appears in the filter form.

It seems that regular fields set under “Subject” → “Data” → “Filter” will show first (which is fine). After that the reference lookups, but I cannot figure out what controls the order in which those reference lookups appear in the form.

In a situation I have made 3 available and for clarity I would like to change the order to a more fitting one. What can I influence to change this?

 

 

Best answer by Erik Brink

There is currently no setting available to influence the order of the lookup references. You are correct the always visible items are currently ordered by type: columns > Lookups > Detail tabs.

All active filters are at the top.

4 replies

Erik Brink
Moderator
Forum|alt.badge.img+5
  • Moderator
  • 548 replies
  • Answer
  • November 12, 2025

There is currently no setting available to influence the order of the lookup references. You are correct the always visible items are currently ordered by type: columns > Lookups > Detail tabs.

All active filters are at the top.


  • Author
  • Superhero
  • 148 replies
  • November 13, 2025

@Erik Brink Thanks for the clarification. Is configuring the lookup references in the filter form already something that planned or should I create an idea for that?


Erik Brink
Moderator
Forum|alt.badge.img+5
  • Moderator
  • 548 replies
  • November 13, 2025

I think you should just be able to order the lookup references in subjects > data, or would you be able to shuffle detail and lookup references too? Or even put them somewhere between the columns.

If it is just lookup reference ordering, you can create a ticket for product SF. Else we can convert this conversation into an idea.


  • Author
  • Superhero
  • 148 replies
  • November 13, 2025

@Erik Brink Just the sorting of the Lookup References for the Filter Form will suffice. TCP ticket created: 13852S