Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Friends,
I have 2 calendar object and one bar chart. I need to select start date from 1st calendar and end date from 2nd calendar.
The data should be displayed for the selected range in bar chart.
Please help me out how to achieve this?
Below are the 2 tables i have.
A:
Month | Billing Amount | Paid Amount |
(in Millions) | (in Millions) | |
1/11/2014 | 1.1 | 1.15 |
2/13/2014 | 1.2 | 1.1 |
3/13/2014 | 1.15 | 1 |
4/13/2014 | 1 | 1.1 |
5/10/2014 | 1.1 | 1.2 |
6/13/2014 | 1.2 | 1.3 |
B:
Month1 | National | State | Hospital |
1/13/2014 | 13.2 | 13.4 | 13.3 |
2/13/2014 | 12.1 | 12.4 | 13.6 |
3/15/2014 | 11.3 | 11.5 | 13.1 |
4/13/2014 | 13.2 | 13.1 | 13 |
5/13/2014 | 11.4 | 11.6 | 12.9 |
Kind Regards,
Anitha
You can achieve this by either providing two buttons each with different time calender and use the one in your expression with set analysis as date should be in range of the two
what are the bar chart
dimension and expression?
Hi Anitha,
Better way i would like to suggest you.
Create one master calendar, and use that master calendar date and your A and B calendar date in set analysis.
Hope you understand this.
- Regards,
Vishal Waghole
Can you please help me out ?
Take billing amount as Dimension
Expression can be any, say ex, sum(state)
Can you please explain. I dont understand
Anitha ,
Actually the selection for two different date fields depends on the linking .
The association of time dimensions should be perfect with the data model
Hi,
I have used the following in the past:
sum({$<Month={$(=MonthName)}, Year = {$(#=Only(YearNumber))}>} SummedValue)
I created a table in QlikView with just the years and the months of the tables that I was interested in - you can obviously do this with just dates as in your example. The advantage of this approach is that you can set the list bar to select only one value from the underlying values. So the table holds the fields MonthName and YearNumber and the Month and Year are fields in your fact table.
This was a simple solution and enabled me to use the same date for a whole variety of fields that did not have to be linked in the underlying schemas
I hope that this helps
R