I'm pretty new to QlikView and am stuck on the following problem:
I've got fincancial data with several date columns (p.ex. transaction date, processing date, billing date, etc...). In order to get a call-date analysis I'd need to set a limit to all those dates at once (e.g. applying a maximum to all columns simultaneously).
Here's an example that uses a variable to filter a date filter. You should be able to include this in your model and add more "Select in Field" actions to the button, or even better, the onchange trigger of the variable that you can find in the Document Settings -> Triggers.
I'm still not sure what you expect to be selected if the same record has a billing date of 15 Jan 2012 and a transaction date of 1 Jan 2012. If you filter on 10 Jan 2012 would you see that record as selected? And if you see that record as selected the billing date of 15 Jan 2012 will not be filtered out. Does one row have the 3 dates defined? Or maybe, in your model one row doesn't have more than one date associated with it, but if that's the case you could put all the dates into one date column and avoid using variables and actions.
If the example is what you need, forget my comments, but if you need additional help, please try clarify these points.
Create a master calendar (or just a date field, e.g. Date) as a logical island, and use it for selections. In your charts expressions, where you use other dates, use conditions or set analysys, e.g. sum({<"processing date"=P(Date)>} Amount)
Would the filter grab all rows with a transaction date less than max date or a processing date less than max date or a billing date less than max date? For example, a row has a transaction date less than the max date, but a billing date greater than the max date, what do you want to happen?
First of all sorry for the late answer... the forum kept telling me "There was an error in sending your answer" for quite some time.
@Michael:
On paper I was thinking about a principle like you suggested, but I did not know the right expressions in Qlikview. Now I've got something to look for in the help file.... thx
@Karl:
The filter would grab any value in each column older/equal than max date. As an example:
Here's an example that uses a variable to filter a date filter. You should be able to include this in your model and add more "Select in Field" actions to the button, or even better, the onchange trigger of the variable that you can find in the Document Settings -> Triggers.
I'm still not sure what you expect to be selected if the same record has a billing date of 15 Jan 2012 and a transaction date of 1 Jan 2012. If you filter on 10 Jan 2012 would you see that record as selected? And if you see that record as selected the billing date of 15 Jan 2012 will not be filtered out. Does one row have the 3 dates defined? Or maybe, in your model one row doesn't have more than one date associated with it, but if that's the case you could put all the dates into one date column and avoid using variables and actions.
If the example is what you need, forget my comments, but if you need additional help, please try clarify these points.
Thank you very much for the example file. I didn't think of the possibility to use a button, but in the end its exactly what my collegues (who will use the report) want.
However I still have troubles to find the right Syntax for limiting multiple date fields with just one button (see images attached - sorry for the system being german).
Wiley_E
P.S: Just to clarify my intentions:
The three time columns are completely independent, so I can't merge them to one.
Example: A clerk handles today (2012-01-25) a bill with billing date 2012-01-24 by completing a cheque deliverable at 2012-02-01 (But if he/she would work faster and by e-trans all three dates would be the same).
I hope I managed to explain, why I have three different data columns
After some more experimenting I found the solution to my remaining problem.
I always tried to get multiple fields into one action, completely ignoring the fact, that I can add more actions (although Karl told me so, I now recognize).
Well finally my report is working!
Thanks to all (and especially Karl) for your help.
