Is there a way to achive this with QuickSight with 1 column and it should still be possible to filter it.
I prepared something in arena (Image Grid test) - it’s just one column with the values 1-10 and i would love to order it like this in a table:
1,2,3,
4,5,6,
7,8,9,
10
rather than 1,2,3,4,5,6,7,8,9,10 or
1,
2,
3, etc.
Hello @robert.eibers, I am thinking you will need to do 2 things to make this work. First, you can use the highlighted arrow icon to swap the rows and columns in your table visual:
Then, you will likely need to create a calculated field for each row to only return the number of values you want. Something like this:
Row1 = ifelse(in({images}, ["1", "2", "3"]), {images}, NULL)
Then you should still be able to filter the images, but it would impact the number of images on each row. This should at least be able to get your started though. Let me know if you have any questions!
great solution! My problem would be that i have more than 100k rows - technical it would be 1-100000 etc. Is it possible to iterate through the numbers? Or can i make your calculation dynamical?
I don’t really see a solution for a big case but for a smaller one i will remember your solution.
Hi @robert.eibers
are we limited to QS or do you have a database in the backend?
Should the grid be flexible in rows and columns or can you fix the columns?
BR
there is a database in the background - we will use different views to find a possible solution. If I have something I will let you know. The grid can be static with a set number of columns but we need to use different filters on.
Hello @robert.eibers, do you have an update on whether you were able to resolve this issue? If not, let me know what changes you made in the views and I can try to guide you further. Thank you!
Hey @DylanM ,
sorry for the late reply. I mark Erik’s answer as a solution because a gallery is quite possible but only with a database in the background.
Our approach is to use two tables, one with custom sql for the gallery and another that comes normally from the database. The images are filtered via database parameters - which are then also named in the custom sql. That works so far, we are now trying to find out how other parameters in the analysis can influence the database parameters. But that would also be a topic for another question.
BR
Robert
Hey @robert.eibers, I appreciate the follow-up. Thanks for resolving this topic. I’ll keep an eye out for another topic if you have questions about linking the analysis and dataset parameters to handle the filtering so I can assist you further. Good luck!