Filters for Horizontal Scrolling Repeating Groups

[freenudge]

Scenario:

I have created a horizontal scrolling repeating group to showcase screenshots of client projects and the company names below the screenshot img.

I have my option set Project Screenshots with 25 options, so I have project screenshots’s img, and project screenshots’s display which work great.

Issue:

I have all of the company names but not all of the project screenshots in my options attributes. How can I filter or set dynamic data to not display if no project screenshots’s img has been uploaded?

Ideas, thoughts, and guidance would be greatly appreciated.

[littlerobot]

Hey @freenudge! Welcome to the forum. I think your quick solution is to add a filter to your repeating group data source. So it will look something like this: All Project Screenshots:filtered, and then your filter would be, Constraint: This Project Screenshots img is not empty. This should now just show the ones that have an img added to them.

I will add that using a Data type instead of an Option set might be a better route for you. That way you could add a constraint to the search instead of having to filter client side, and if you ever have to update info dynamically it could be easier. If I misunderstood your use case though, just ignore that advice.

Hope this helps!

[freenudge]

Thanks. I ended up creating a filter on the Option Set data as show in the screenshots.

[boston85719]

@littlerobot

So it will look something like this: All Project Screenshots:filtered, and then your filter would be, Constraint: This Project Screenshots img is not empty.

Don’t do that. It will return all results of All Project Screenshots and require client side filtering which is dependent on client device computing power in regards to speed to process filter, so inconsistent across devices and some may be slow.

Don’t use the filter operator, just put the constraint on the search itself, so that you will one save money on WU costs as you will return less results from the database to the device, and two have a faster search result due to the filtering happening on the server rather than client device which is always faster.

My above statements were based on assumption the screen shots are a data type and not an option set

After re-reading your original post, why are you using options sets instead of a data type for this? Reason I ask is it is not clear what your app is used for, since an option set approach is okay if the app is used just by one business and they will upload via the editor, but if it is to be used by multiple companies that will upload via pages and uploader elements, then it needs to be data type as users can not upload option set values from pages or upload elements and can only do so via the editor.

[freenudge]

Thanks for the breakdown. This is my new home page for my business hence why I opted for using an Option Set as I will be managing the display.

[boston85719]

When working with options sets the only way to filter is via the filtered operator, so no worries with that then.