Hi
In the TM1ProcessError Log I am seeing the following :
Error: MetaData procedure line (0): Insertion of leaf "XXXX" into hierarchy "HHHH" failed because a consolidated element by that name already exists in the dimension.
However, in the TM1Server.Log it says
2016 [2] WARN 2019-11-18 18:28:51.877 TM1.Dimension DimensionUpdate on 'DDDD' failed: can't retype a leaf to a C element when there are other instances of the leaf in one or more other hierarchies.
2016 [2] ERROR 2019-11-18 18:28:51.890 TM1.Process Process "PPPP": : Execution was aborted. Error file: <TM1ProcessError_20191118182851_87702016_PPPP.log>
The TM1ProcessError log file message seems to imply that I am trying to insert an element as a Leaf level when it already exists as a Consolidation in one of the hierarchies of the dimension.
The TM1ServerLog file message seems to imply the opposite that I am trying to insert an element as a consolidation when the element already exists as a Leaf in one or more hierarchies.
The TM1Server Log is the correct message.
However, the TM1Server Log is listing this only as a WARN but it actually causing an error, so the severity level needs to be corrected on the TM1Server Log and the message going out to the TM1ProcessError Log needs to be corrected.
The code to work around the issue of avoiding element type conversion for both Child and Parent took around 60 lines of TI script. My preference would be that, if the element already exists as a Leaf and I try to insert it as a C then it just ignores the insertion and does not issue an error message. If I actually link a component element to a leaf level element then it should automatically become a consolidation without any error message, which does seem to be the case.
If I attempt to avoid this error by always inserting elements as N leaf level
Regards
Paul Simon
------------------------------
Paul Simon
------------------------------
#PlanningAnalyticswithWatson