Deleting Missing Transaction Data

Kalle

I have Transaction data import set up in Data Hub. The data has no ID so I use a numbered list to create a list (Transactions #) of unique ID:s by combining a few properties. I then load all of the properties into a details module with the Transactions #- list as a dimension. 

 

Data is loaded every night and it consists of transactions from the last 60 days. If a transaction is cancelled the row disappears from the import file and of course I need to make it disappear from Anaplan as well. The rows that are older than 60 days should stay intact. I did figure out a way to achieve this but can´t help to think that there could be an easier way to do this. So I would love to hear your suggestions.

DavidSmith

Firstly really push to get a unique key in the data file.  It makes all of this so much simple and faster.  Importing with Combination of properties is so much slower than using a code, and you have no option but to import into a list property rather than a module, going against DISCO and System modules best practice

 

But, that said, this is a recommended approach that can use used for transactions with or without a key

1.  Given you have a 60 day cutoff, you will need to maintain a date field somewhere.  this could be imported every day, or manually input.  You can use this to flag those transactions to keep

2. If you can, add a column to your data file that is a boolean so that all rows are set to TRUE

3. In your transaction list or module, add a property/line item to hold this Boolean flag

4. As the first part of the import, clear out this line item

5. Import the data as normal including the new "imported" TRUE field

6. You can now check for those without TRUE

7.  Delete those rows that have FALSE in the import field, but not those over 60 days

 

I hope that helps

David