Question regarding using Import to List, Trans, Calculate Attribute (multiple line items) for better performance : what is the plan to achieve performance when the code doesnt hold all attributes in 60 characters ? Do we use list properties ? Do we use one attribute that is loaded and can be used then to calculate all other attributes. If so, what is a performance to have 1 list code, 1 line item attribute and the rest calculated (e.g. compared to multiple line items attributes loads)
Another question regarding delta loads : how do you perform the clearing of the "new data" boolean if we have like 4 or 5 spoke models that are "connected" to the data hub
Thank you for the good article! Just a friendly reminder - "The Anaplan Way" link is not working.
@rob_marshall question on scheduling of Data Hub to spoke integrations. If for example you have 3 spoke models that need to import data from the data hub. Does each spoke import action from lock the data hub from performing other spoke integrations? This is related to the scheduling of imports from the Spoke models. If I schedule integration of 3 spoke models at the same time, e.g. 3am vs scheduling them sequentially spoke 1 integration first then spoke 2 integration next, etc … could you please advise on this
Great question and the answer is no because you are only reading the data from the data hub and that doesn't lock it (assuming you aren't writing anything back to the data hub). Models only lock if you are writing data (so the spokes would be locked), but not the data hub.
Let me answer your questions in reverse order:
Another question regarding delta loads: how do you perform the clearing of the "new data" boolean if we have like 4 or 5 spoke models that are "connected" to the data hub
Answer: Put the clearing of the boolean as the first action to load the data hub. In doing this, multiple spokes can take advantage of the delta load.
Codes with greater than 60 characters
Answer: There are a couple of ways of accomplishing this, but none are great.
Ok, so about delta load. How do you make sure that spoke model got all the previous deltas correctly before the next delta load just removes the boolean ?
My understanding is that spoke models use dathubs as central data source in a "pick latest data" way + as imports are pull only, there is no way i can think of that would ensure data timeliness and consistency between dat hub and spoke models with this delta feature.
Sorry for the continuous questiond, but we are looking into the delta loads questions and i cannot see how anaplan can achieve something resilient enough here.
Ok, good question. There are a couple of ways:
Does that help?