topic Re: Retaining incremental data in QlikView

Retaining incremental data

Pulkit_Thukral — Wed, 25 Nov 2020 16:16:04 GMT

The requirement here is that daily incremental open ticket dump comes in every 2 hours.so it should overwrite the previous dump for that day .

Also,the last dump for that day (12 th Dump) should be saved to keep the tickets history saved for that day when compare to some future date.

Ex-

2 am first dump came with 1000 tickets.

4 am second dump came with 1100 tickets which has some new tickets (logged and open between 2 am to 4 am) plus the old still opened tickets.

So,4 am dump should overwrite 2 am dump and similarly 12 am dump should be retained to save ticket history for that day.

Re: Retaining incremental data

vikasmahajan — Wed, 16 Mar 2016 05:22:56 GMT

What is data source ?

Whether you are using sense Or Qlik

Whether primary key is there in your data ?

Create some samples excels and post.

Vikas

Re: Retaining incremental data

Pulkit_Thukral — Wed, 16 Mar 2016 06:24:06 GMT

Data source - .csv files with same name and this csv file is generated every 2 hourly.

Tool-Qlikview

primary key - Yes

Sample:-

Dump at 16th March 10 pm:-

ID	Status	CreatedTime
1	Open	16/3/2016 9pm
2	Open	16/3/2016 4pm
3	Open	10/3/2016 4pm

It has all the open tickets as on 16th march 10 pm.

Dump at 16th March 11:59 pm:-

ID	Status	CreatedTime
4	Open	16/3/2016 11pm
2	Open	16/3/2016 4pm

It has all thee open tickets as on 16th March 11:59 pm.

Note:1. Ticket ID 4 was logged between 10 pm to 11.59 pm .Hence, it is a new entry.

2. Ticket ID 1 and 3 Were resolved hence removed from the latest open dump.

Also,The requirement is that 11:59 pm dump should overwrite 10 pm file and also the same file(11.59 pm) should be saved(retained) for that day so that if for example we want to see 16 th march data on some day later.So selecting 16 th march from calender should give us data from 11:59 pm dump(as it is the last dump of 16th March).