TM1 Forum

Is there a way for the system to "re-sync" the Leaves hierarchy within a dimension if it gets out of sync? By this, I mean we have alternate hierarchies with leaf elements that do not exist in the Leaves hierarchy. This resulted from an incomplete migration of objects for the dimension.

Have not found anything. Have restarted. Have tried "tricking" it into rebuilding the Leaves hierarchy by the direct functions, but to no avail.

Looks like we'll have to use a TI to do it.

PavoGa wrote: ↑Wed Nov 14, 2018 5:04 pm we have alternate hierarchies with leaf elements that do not exist in the Leaves hierarchy.

My understanding is that this should simply not be possible. A leaf in any hierarchy must also exist in the Leaves hierarchy.

I guess when you say it resulted from "incomplete migration" you mean a "cold" migration of .dim files from one instance to another and a restart?

lotsaram wrote: ↑Wed Nov 14, 2018 7:23 pm
I guess when you say it resulted from "incomplete migration" you mean a "cold" migration of .dim files from one instance to another and a restart?

That is exactly what I meant. Did a cold migration and the different instances have different hierarchies and elements within those hierarchies over time. This between DEV instances. Do not expect it in QA/PROD.

Anyway, wrote a process that ensures everything in Leaves stays copacetic.