Problems Or Limitations With The Dynamic Filter Addon
S-D CONSULTING
Hi, I need some information about dynamic fields, especially the use of the Dynamic Filter add-on.
To understand if the problems I encountered were due to my limited knowledge, I used your Revstat template, from a hypothetical real estate agency, as a test.
In that demo, I saw that the tab add-on was used to filter the apartments, within which collections were then created, filtered using another collection called Property Category.
I found a limitation. If I wanted to use the Dynamic Filter add-on, it would allow me to perform search queries, but it wouldn't allow me to do so if the selection fields are part of another collection.
To clarify, still using the Revstat example, if I wanted to insert a Dynamic Filter above the tab, and I wanted this filter to use the Property Category, I couldn't do so. I can only do this on the custom Type field, which is a free text field, but not on the collection.
https://app.screencast.com/wqfl2CUQBxSz6
Yet the collection filter allows this operation, but it's not provided by the Dynamic Filter. Why this limitation?
Thanks
Ofi Khan
Accepted AnswerHello S-D CONSULTING,
Thank you for your detailed explanation and for testing with the Revstat template. I appreciate the effort you put into understanding how the Dynamic Filter works.
Regarding your observation: yes, the Dynamic Filter add-on currently has a limitation in how it handles fields sourced from other collections.
The Dynamic Filter add-on only supports filtering based on:
- Fields inside the same collection
- Custom fields (such as text, number, select, etc.)
It does not support filtering using fields that originate from another collection, even if the Collection Filter add-on allows this type of relationship. This is why the Property Category (which is another collection) cannot be used inside the Dynamic Filter, but a free-text field like Type can.
This is expected behavior at the moment and not a bug. The two add-ons use different filtering mechanisms:
- Collection Filter is designed specifically to work with inter-collection relationships.
- Dynamic Filter is designed to work with standalone dynamic fields and does not yet support cross-collection filtering.
For more details, you can review our documentation here: https://www.joomshaper.com/documentation/sp-page-builder/collection-filter#other-dynamic-filter-options
We fully understand that cross-collection filtering through Dynamic Filter would be very useful. I have already shared this as a feature request with our product team for future consideration.
If you have any additional use cases or examples, feel free to share them — they help us refine the feature roadmap.
Best regards
S-D CONSULTING
Accepted AnswerThanks for this lengthy reply. I had a hunch about the issue, and I understand that Dynamic Filter is also a new product, evolving, and allows for a lot of things.
Where I didn't have the functions, I created them with a bit of programming—js and jQuery, or simple PHP—but it's easy to find the solution.
I'm happy to provide feedback. I found a small issue and I'll report it in another ticket. It concerns the use of the "title" field.
Ofi Khan
Accepted AnswerThanks for your feedback and test cases.
I have a humble request. It would be very kind of you if you can manage some moment to give us feedback on
This will inspire us to improve.