topic Working with Range Doubt in QlikView

Working with Range Doubt

Thu, 02 Jun 2011 21:11:48 GMT

Hello everyone.

I'm at this point trying to develop a new qlik view tab. I started making filters to the data, but one of then is not working as i want. I need a date filter, but i wanna work with a range, the start date and the final date. The result set must be the rows with column's value between the range.

Is there a way to make two text box to watch for the limits of the range ? Or something that gives me this result ?

Thank you so much for the help .

Working with Range Doubt

hectorgarcia — Thu, 02 Jun 2011 22:27:23 GMT

hi can you put a small example in a file to conceptualize better your need

Working with Range Doubt

johnw — Thu, 02 Jun 2011 23:11:40 GMT

A slider object is an easy way to manage a range of dates in some cases. Or sometimes people make two date variables, and trigger selection of dates between the two any time either variable is changed. There are probably other approaches as well depending on what you're after.

Re: Working with Range Doubt

Thu, 02 Jun 2011 23:21:22 GMT

Hi, thanks for the reply hgarcia.

Here an example... i have a field, a date type field, its a collumn on a table. I want to make a filter to act as a range on this collumn.

My ideia is to have, i don't, maybe two input boxes, one to insert the start date and another one to insert the final date then the data would manage itself having those limits as extreme points.

Thanks again

Hi John.

Your suggestion to work with variable seems to what i need, i think, i tried before but i only were able to work with variables in calculations. Do you have some example with date been triggered by variables acting like extreme points ?

I tried the slider, but with each selection the role of data get's smaller and you have to keep cleaning it, there was also a legend's value problem ... so i did not work for me.

Thanks for the help.

Re: Working with Range Doubt

johnw — Thu, 02 Jun 2011 23:58:09 GMT

Here are three separate solutions that behave very similarly. One uses only the data model to narrow down the possible dates by the specified end points with no selections being made in the date field itself. One makes the date field selections with a macro. One makes the date field selections with actions.

Edit: I tend to prefer data model solutions where practical. The data model solution here can add a lot of extra date data, but would probably still not bump up the size of a typical application by very much. But it COULD cause problems if the application covers a very long period of time.

Re: Working with Range Doubt

Fri, 03 Jun 2011 20:28:59 GMT

Thank you som much John, i used the last example an it worked great for me.