You should use the built-in tags feature for your topic-tags.
- Tags Help Center article
- Querying content based on one or more tags - CDA documentation
You should use the built-in tags feature for your topic-tags.
Tags can help to use multiple tags for filtering on contents in general, but it doesnât help if youâve got two different content types linked to the same reference field.
Example:
Youâve created a new content type âPersonâ and have a field called âHobbiesâ. To have a description for each hobby the âPersonâ has, youâve entered a content type for each hobby like a content type called âSportsTypeâ and one called âFavouriteVehicleTypesâ with different attributes. Now you want to add both âsportsâ and âvehiclesâ to the Hobby reference field. In the Frontend you now have to check for some Person that just likes âsoccerâ. You wonât be able to do this lookup as far as Iâve understood. In my project I had a similar case and a switch to multiple reference fields only linking to distinct content types was necessary (Iâm using GraphQL and in SQL obviously such queries are standard).
The example is constructed and not 100% valid, but it explains the issue.
Searching on multiple references would be a nice feature.
Kind regards
Marc
I just needed this and ran into this problem. This is absolutely a necessary feature. And I must agree that the documentation doesnât indicate this restriction well, so even when I saw functional code in the documentation, it wasnât clear too me it wonât work on multi-reference fields.
Iâll probably use tags then instead, but they of course have their own restrictions.