Currently building a model which involves import of data at various stages.
Wanted to implement a functionality where i can keep a check on the imported data to be validated after each import is run.
Any suggestion would be great help.
Solved! Go to Solution.
Can you further narrate what you mean by "keep a check on the imported data to be validated after each import is run."?
Hi Lip Chean,
So there are multiple import actions in the model that i have made.
I need to publish a dashbaord that would prompt if there are any errors or mismatches or if the actions have run successfully.
This is to make sure that the files being uploaded/imported into the model have identical names and with the dimensions/list items and numbers in the model.
Hope this gives the required details.
You can refer to the Data Hub best practices link below, particularly the 'Reconcile' segment.
As @LipChean_Soh has pointed to, the best practices here is to utilize the FINDITEM() function to determine where your data loads have resulted in metadata mismatches between your source system and Anaplan. First off, you should be importing your source data into text-formatted line items in a flat, 2-dimensional module so that they don't immediately kick out (since text will always be imported kickout-free). Second, create a new list-formatted line item that points to the text-formatted line item. Third, create a validation boolean-formatted line item that can show where there are invalid line items.
Line Item . Format Formula
FI Cost Center List [Cost Centers] FINDITEM('Cost Centers', 'COST_CENTER')
Valid CC? Boolean IF ISBLANK('FI Cost Center') THEN FALSE ELSE TRUE
There are more advanced techniques that you can utilize to further enhance validations as well as ways to make this process more efficient, but this is the basic premise. Beyond this, you can then filter your module on invalid instances of the 'Valid CC?' boolean-formatted line item and publish that filtered view onto a validation dashboard. Hope this helps.
I agree with everything you stated above except for importing into a two dimensional module as metadata and transactional data should be kept separate. By keeping them separate, you will save space as the metadata should not change over time except if you are doing something similar to employee department transfers.