I'm just going to go with 'all of the above' and hope for partial credit. After all, with Essbase, it's always a bit of a guessing game, right? Maybe we should just ask the Magic 8-Ball instead.
D. Data cannot be input to the parent in target versions. Dynamic Calc means the values are calculated on the fly, so you can't manually override them. Seems pretty straightforward to me.
Hmm, I'm torn between A and C. Maybe both? Essbase data blocks could shrink, but that might come at the cost of slower performance. Tradeoffs, you know?
I'm going with B. The member is not available for process management. Dynamic Calc members can't be used in calculations or reporting, so they're essentially disabled.
I think the correct answer is C. Retrieval performance could be slower when referencing the parent entity member. Dynamic Calc can impact query speed, especially for aggregations.
Alishia
6 months agoCorinne
6 months agoJustine
6 months agoDong
5 months agoLevi
5 months agoRachael
6 months agoArlette
6 months agoMaurine
5 months agoKatlyn
5 months agoScarlet
6 months agoSlyvia
6 months agoKeneth
6 months agoGolda
6 months agoWhitley
6 months agoMozell
7 months agoYoulanda
6 months agoPansy
7 months ago