Hello dear community, I am relatively new to QlikView and I still have a lot to learn.
I have data from 2 different databases , Database1 is with Service Requests Database2 is with Sales
I have connected the 2 databases through Contract_ID ( its present in both databases)
My question is is it possible to make a filter which filters both databases . Let me clarify
For example if i choose year 2017 - month January from Service requests
it will show me all values generated in that period
IS it possible to show me also all values generated in Sales database?
The field which i generate the Month and Year fields are different in both databases. But i want to make something like if i choose January 2017 from service requests, to show me also all sales in this period
You may have two difference data sources but after loading into QlikView all your data resides in your QV data model and you shouldn't think of filtering two different databases any more. It's difficult to give firm advice without knowing anything about your data but I think your first step should be to create two master calendars - one for sales dates and one for service request dates.
Sometimes this might be enough but because you want to look at sales data and service request data against a common date dimension you need to take a further step and construct a canonical calendar. If all this seems difficult here is the definitive guide to this topic:
although this may work, it's probably not a good idea. Triggers rarely are, though granted they do on occasion serve a purpose.
Consider this scenario:
Contract ID YEAR1
Contract ID YEAR2
Now, what happens if your user selects 2016 in YEAR1?
QlikView will only associate the Sales in that year, then your tirigger will fire and further reduce the data in YEAR2. So your end product will be filtered to the second and third rows in Service Requests, however the second row will be filtered out based on YEAR1.
In this instance your filters will act as an AND condition rather than an OR. You will filter where Sales year is 2016 AND Service Requests year is 2016.
The solution to this is as stated before - model your data. Others have suggested a master calendar, which is a valid suggestion, however a first step towards this (in order to avoid a circular data model) is to set up either a concatenated fact of link table data model.