It would be very helpful to be able to access the list of reference items on a given CMS page. It would reduce both developer and client friction, time, and errors. OR, enhance filtering to be able to match a reference field.
Basically think of the following example:
I have a collection 'Hotel Rooms'
I have a collection 'Hotels'
On the Hotel Room template, I want to show other rooms from the same hotel.
The way you do this now is for every Hotel room, you need add all other hotel rooms from the same hotel in order to do this natively.
If you have 5 hotels with hundreds of rooms each, the native approach is obviously absurd to manage.
It would be much more natural to simply assign Hotel rooms to a multireference field in Hotels. And then reference a hotel from each hotel room. That way we are managing one list.
Alternatively, you could simply add a filter: This Hotel Rooms Hotel = Current Pages Hotel.
Even better, and much more robust, allow us to insert dynamic values into the filter field. This way we could use a text field to identify these relationships across so many more use cases.
Benjamin Churchill
.svg){kind=logo}
our suggestion to streamline the management of reference items in a CMS page is spot-on. Implementing a multireference field in the Hotels collection to manage Hotel Rooms would indeed simplify the process, reducing friction for both developers and clients. Alternatively, adding a filter like "This Hotel Rooms Hotel = Current Page's Hotel" or allowing dynamic values in filters would also greatly enhance flexibility and efficiency. This approach would make it much easier to handle large datasets and maintain relationships across collections. Thank you for sharing this valuable insight!
Best regards
ADP Vantage
I completely agree! Being able to access multi-reference lists or add dynamic filters would streamline managing CMS content significantly. It would simplify showing related items like hotel rooms, reducing errors and saving time for both developers and clients.