Skip to main content
Question

Recommended approach for sharing filters between users in IFS Cloud

  • March 13, 2026
  • 2 replies
  • 148 views

Forum|alt.badge.img+3

Hello,

we understand that, unlike in IFS Applications 10, there is currently no standard functionality in IFS Cloud for sharing or copying saved filters between users.

However, we have a customer requirement where multiple users need to work with the same predefined filters.

Could you please advise:

  • What is the recommended approach in IFS Cloud to provide the same filters to multiple users?

  • Are there any best practices or workarounds (e.g., lobby elements, configurations, exports, or other approaches) that could be used to distribute or replicate filters across users?

Any guidance or experience from similar implementations would be appreciated.

Thank you.

2 replies

Forum|alt.badge.img+8
  • Do Gooder (Customer)
  • March 13, 2026

We have not figured out how to share filters, but we do share searches.  Can you accomplish the same thing with a search instead of a filter?


Forum|alt.badge.img+9
  • Hero (Partner)
  • April 3, 2026

Hi ​@jaroslav.runstuk ,

What’s happening

  • Saved filters in IFS Cloud:
    • are user-specific
    • stored per user/session

 So:

  • no native way to:
    • share
    • export/import
    • assign to multiple users

 What people usually do (workarounds)

✔ Option 1 — Lobby elements (most common)

  • Create:
    • Lobby → List element
  • Apply:
    • predefined filter in the data source

 Then:

  • assign lobby to multiple users

✔ Everyone sees same filtered data
✔ Centralized control

✔ Option 2 — Saved searches via configuration (limited)

  • Define:
    • custom projection / view
  • Apply:
    • filter logic in projection

 Acts like:

  • “pre-filtered dataset”

✔ Option 3 — User training / manual setup

  • Share:
    • filter criteria
  • Users:
    • recreate filter manually

 Not scalable, but commonly used

✔ Option 4 — Page personalization export/import (partial)

  • In some cases:
    • page config can be exported

 But:

  • not reliable for filters specifically
  • depends on page type

✔ Option 5 — Custom solution (advanced)

  • Store filter definitions:
    • in custom table
  • Apply via:
    • customization / extension

 Used only when requirement is strong

 What does NOT work

  • ❌ No global filter library
  • ❌ No “share with users” option
  • ❌ No standard migration of saved filters

 Best practice (from implementations)

 Use Lobby elements when:

  • same filter needed by many users
  • reporting/dashboard scenario

 Use projection filtering when:

  • business rule-based filtering is needed