Incremental data export to interface (informatica)

Hi All - I am looking for design suggestions to below the following use case. Please guide me . Thanks

1. We have a module for employee - role mapping (1:M)

2. Planners have an option to change employee role (add / delete)

3. There are other downstream systems looking for modified employee -role mapping data. Hence, the expectation is to send the data to our interface(Informatica) in near real time

4. I need to send both old role and new role details. Again, the expectation is to send only the employees for which mapping have been altered

Please guide me. Thanks.

Accepted answers

All comments

nathan_rudman

I'd do this over time dimension.
Role can be overridden and if so, it becomes the new roles (IF isnotblank(override) THEN override else previous(role) ) . System always export the latest month. You can detect a change with PREVIOUS(role) <> Role

RajeshPrabhu

Thanks Nathan. Please advice the purpose of time dimension

Going by the suggestion just excluding time dimension, Can I not achieve the same result with 3 line items : role , new role and overridden (role <> newrole) boolean.

In export process

1. Exports only items where overridden = true.

2. Replace role with new role which will eventually reset overridden flag to false for all items and ready for next set of the changes

rob_marshall

@RajeshPrabhu

Take a look at this course which speaks to Delta Load processing.

https://learning.anaplan.com/enrol/index.php?id=1265

Rob

Quick Links

Can you help?

Unanswered questions

Dimensionality - Formula Help
I have a Price module where customers are ranked based on their unit prices. I also have a Comparison module, where I want to display the names and unit prices of top-ranked customers for comparison. The model includes a Customers list. In the Comparison module, I want to write formulas to bring in the customer names and…
Can there be a duplication in Process ID's
Can there be a duplication in Process ID's
Using Polaris and Classic
Client has spoke models built in Classic and now considering building Data Hub in Polaris in order to deal with sparsity. On the surface this seem possible but likely a bad idea. Has anyone done anything similar to this? Specifically, what did you have to do to ensure that data was compatible? Any thoughts or suggestions…