In the scenario where my Ticket (data structure with associated “tags”) has the tags {a,b}, and the user selects filtering based on tag {‘a’}, my RG is not showing this ticket.
If you haven’t yet, check Privacy rules if that is hiding other Tags or Tickets.
Also just a side note, move the Status constraint to the Search for better performance. Better to let the server-side search reduce down the number results before the client side :filter has to filter more.
The logic seems fine, you could try removing the first filter and also unchecking the “Ignore empty constraints” just to make sure there’s no issues there.
Does your search have it’s own constraints getting in the way?
And other operators after your filter in the Repeating Groups data source?
Has the repeating group had more than 1 item before? Make sure there’s a enough room to seem more and it’s not set to static # of rows and columns
Also make sure your database actually has the data you expect to see
The example I gave filters a Repeating Group based on a list of elements (tags) selected in the multidropdown, showing the elements that have items in common (intersect with)…
It seems that this is exactly what you are trying to do…
Again, appreciated, but I have this exact logic implemented. You can see the screenshot in the beginning of the post. For some odd reason, this is not performing as expected on my app.
Also, vis-a-vis testing - even if those tags were stored properly, there’s very little test data in here and as far as Tickets that have more than 1 tag, it looks like there are only intersecting tags for “Repairing”? (Which I believe would net you two Tickets were this implemented properly.)
ok sorry i don’t completely follow. Why does each Tag field within Ticket only have a single text? It’s a list, right? When i create a ticket, i add in the selected list of tags. Shouldn’t this append to the end of the existing (empty) tag list?