topic Which way is better? in QlikView

Which way is better?

fcecconi — Fri, 24 Apr 2015 15:41:57 GMT

I am currently creating an application and the users would like to see multiple charts and list boxes on a given tab. However he doesn't want to see everything at once. Is it better to use buttons to show and hide the objects as needed or create multiple containers and then add then to a 'master' container on the page? What I would really like to do is add a 'tab component' on the sheet.

Thanks in advance for your advice!

Re: Which way is better?

buzzy996 — Fri, 24 Apr 2015 15:43:19 GMT

i think using container object is good

Re: Which way is better?

Anonymous — Fri, 24 Apr 2015 15:45:47 GMT

It depends on your preferences. I don't like containers, for example.

You can create a set of buttons, or better text objects with actions, and align them to each other to look like "tabs", especially if you make top corners rounded

Re: Which way is better?

NickHoff — Fri, 24 Apr 2015 15:54:58 GMT

You could create an adhoc nature to the report, with a listbox displaying all your dimensions, and a listbox displaying the metrics. Create an inline table with an ID and description on each dim or metric. You'll have a show/hide expression for each expression and dimension in a straight table like =SubStringCount(Concat(@AdHocMetricNum,'|'),'001')

You could also include a fast change in the chart to other objects.

Re: Which way is better?

b_garside — Fri, 24 Apr 2015 16:10:02 GMT

I agree. Containers are only useful for very simple implementations. Not much flexibility when using them.

That's why I too use buttons for navigation where you can add actions that opens a host of other options.

Re: Which way is better?

Anonymous — Sun, 03 May 2015 22:19:18 GMT

My preference is using buttons, containers can be helpful if you are not going to have to alter things but they are fiddly to work with.

Re: Which way is better?

fcecconi — Mon, 11 May 2015 18:19:13 GMT

thanks everyone for your feedback. I am going to use the button approach