Steve Rowe wrote: ↑Thu Jan 31, 2019 9:53 pm
Can you remember the creation sequence that led to this? In theory every N level should end up in the leaves hierarchy, if this is not reliable then this is a bit of an issue..
Absolutely agreed!
I have also seen this happen. The behaviour of the Leaves hierarchy should be “maintenance free” for addition of elements. That is if a leaf element is added to the same named hierarchy or any alternate hierarchy it will automatically appear in the Leaves hierarchy. I have found this to be
mostly true but
sometimes the Leaves hierarchy gets "out of sync" and doesn’t contain all the leaf elements from the other hierarchies. When this happens any additional new N elements added to other hierarchies get added to Leaves and elements deleted from Leaves are removed from other hierarchies. But the out of sync elements remain out of sync. The Leaves hierarchy being out of sync also survives a server restart.
This has me really scratching my head as there doesn't seem to be any "sync leaves hierarchy" function, either in TI or Rest API. So when it happens (which has been a handful of times = a handful of times TOO MANY) the only solution is to run a TI that loops over all hierarchies and checks for existence of all leaf elements in Leaves and if Dimix=0 add the element.
Wondering who else has seen this and if anyone has heard from IBM on the issue?