I have data that refreshes once a month to tell me sales for that month. The current pivot table looks like below for the month of January 2025
Totals
46
Brand 1
15
Item 1
5
Item 2
8
Item 3
2
Brand 2
20
Item 1
7
Item 2
9
Item 3
4
Brand 3
11
Item 1
3
Item 2
5
Item 3
3
Once app refreshes the above data will change. I want to be able to have another table that will show the Jan 25 sales, the previous few months of sales and then also the current month of sales when the refresh happens.
You can use the STORE statement to save any table in your app into a QVD file. then you can load from the QVD using a LOAD statement. There is plenty of documentation available here, which should explain how it works: https://help.qlik.com/
The optimal solution though would probably be to get this fixed at source, so that whoever is supplying you with the data includes a year-month field, and just appends each new month of data as it becomes available, rather than just supplying you with the latest month each time. This would be preferable to having a QVD as the single source of truth for historic data. It would also simplify your task significantly, as the only change you'd need to make would be to load the extra field.
I'd store the data into a QVD, with an additional dimension indicating the year-month value.
Each time the app refreshes with a new month's data, assign it a new year-month value, then load the QVD data from last month and append it onto the table in the load script, and then finally store the combined table back to QVD ready for next month's load.
Then you can add a year-month filter to your app to enable users to view whichever month they want.
You can use the STORE statement to save any table in your app into a QVD file. then you can load from the QVD using a LOAD statement. There is plenty of documentation available here, which should explain how it works: https://help.qlik.com/
The optimal solution though would probably be to get this fixed at source, so that whoever is supplying you with the data includes a year-month field, and just appends each new month of data as it becomes available, rather than just supplying you with the latest month each time. This would be preferable to having a QVD as the single source of truth for historic data. It would also simplify your task significantly, as the only change you'd need to make would be to load the extra field.
