Hi, Wondering if anyone has experienced this strange issue.

I have a Product dimension with an Alias of Description. Description is a concatenation of the Product code and the description text, static from import, not rule derived.
Copying and pasting members into the Set editor with the Description Alias on or off pastes as expected and the members are valid.

If I create a Dynamic Report in PAfE with the Product on rows and Description on, the report rebuilds and shows values as expected:


------------------------------
George Tonkin
------------------------------

#PlanningAnalyticswithWatson

Update


Think I have resolved this for now.

I went back to our development server, updated the dimension with the latest master data refresh, updated all attributes, rebuilt all rollups, rebuilt all alternate hierarchies and verified structures.

I noticed that there were quite a few items not in the Default hierarchy but appearing in the Leave hierarchy.  These "orphaned" items looked to be old members from testing, previous loads etc.  It is possible that the members were removed from the Default hierarchy via a deletion from the dimension in Perspectives. (Still need to check if this causes the member to be deleted from the default but kept in Leaves).

I created some MDX to go through members in Leaves and not in the Default hierarchy, and delete them.
This cleaned up the orphaned/ unused members and the two hierarchies seem more aligned.

After a save data, I copied over the Product dimension and the hierarchies from the Product}hiers to Production.
So far so good - PAfE giving DIMIX values where alias is used, TM1Web returning reports with values, not just a blank structure.

Still not sure what happened here or how to prevent it from happening again but would be happy if anyone has anything to add.

------------------------------
George Tonkin
------------------------------

Hi George

Not sure if it is relevant to your issue but we have found cases where you can have base level elements in the classic hierarchy that do not appear in the leaves hierarchy.

To work around this in our standard dimension update routine we copy all base level elements from the classic hierarchy to the leaves hierarchy and then all elements in the leaves hierarchy to the classic hierarchy. That way we are sure that both are in step. If the leaves hierarchy produces an element that does not have any parents then our standard orphan processing catches it.

We are still using PA 2.0.5 so I am not sure if this issue has been cured in a later version. We are testing 2.0.9 at the moment.

Unfortunately, there are a lot of quirks around the Leaves hierarchy, eg inserting an element under an element will now give an error instead of just making it a consolidation as it used to. You need to physically delete it as an N in the leaves, classic and all named hierarchies and re-insert it as a C, and then you will have lost links to all the parents of the element so you need to rebuild those too. Our standard dimension update processes have been growing somewhat to cope with all these quirks.

Regards

Paul Simon

------------------------------
Paul Simon
------------------------------

Original Message:
Sent: Tue June 22, 2021 07:22 AM
From: George Tonkin
Subject: TM1Web-Dynamic Report not returning values but is returning structure

Update


Think I have resolved this for now.

I went back to our development server, updated the dimension with the latest master data refresh, updated all attributes, rebuilt all rollups, rebuilt all alternate hierarchies and verified structures.

I noticed that there were quite a few items not in the Default hierarchy but appearing in the Leave hierarchy.  These "orphaned" items looked to be old members from testing, previous loads etc.  It is possible that the members were removed from the Default hierarchy via a deletion from the dimension in Perspectives. (Still need to check if this causes the member to be deleted from the default but kept in Leaves).

I created some MDX to go through members in Leaves and not in the Default hierarchy, and delete them.
This cleaned up the orphaned/ unused members and the two hierarchies seem more aligned.

After a save data, I copied over the Product dimension and the hierarchies from the Product}hiers to Production.
So far so good - PAfE giving DIMIX values where alias is used, TM1Web returning reports with values, not just a blank structure.

Still not sure what happened here or how to prevent it from happening again but would be happy if anyone has anything to add.

------------------------------
George Tonkin
------------------------------

Thanks for the feedback and information Paul.

I am encountering this with PAoC so probably 2.0.97/8 I would expect on the TM1 server side but have not confirmed.

Still playing around with rebuild sequencing to try and work out exactly when the "break" happens but looks like when I unwind and rebuild an alternate hierarchy which has the parents in that hierarchy updated with Descriptions, the default goes a bit wonky.  Purely conjecture right now as I am still trying to replicate.

------------------------------
George Tonkin
------------------------------

Original Message:
Sent: Wed June 23, 2021 03:05 PM
From: Paul Simon
Subject: TM1Web-Dynamic Report not returning values but is returning structure

Hi George

Not sure if it is relevant to your issue but we have found cases where you can have base level elements in the classic hierarchy that do not appear in the leaves hierarchy.

To work around this in our standard dimension update routine we copy all base level elements from the classic hierarchy to the leaves hierarchy and then all elements in the leaves hierarchy to the classic hierarchy. That way we are sure that both are in step. If the leaves hierarchy produces an element that does not have any parents then our standard orphan processing catches it.

We are still using PA 2.0.5 so I am not sure if this issue has been cured in a later version. We are testing 2.0.9 at the moment.

Unfortunately, there are a lot of quirks around the Leaves hierarchy, eg inserting an element under an element will now give an error instead of just making it a consolidation as it used to. You need to physically delete it as an N in the leaves, classic and all named hierarchies and re-insert it as a C, and then you will have lost links to all the parents of the element so you need to rebuild those too. Our standard dimension update processes have been growing somewhat to cope with all these quirks.

Regards

Paul Simon

------------------------------
Paul Simon
------------------------------


Original Message:
Sent: Tue June 22, 2021 07:22 AM
From: George Tonkin
Subject: TM1Web-Dynamic Report not returning values but is returning structure

Update


Think I have resolved this for now.

I went back to our development server, updated the dimension with the latest master data refresh, updated all attributes, rebuilt all rollups, rebuilt all alternate hierarchies and verified structures.

I noticed that there were quite a few items not in the Default hierarchy but appearing in the Leave hierarchy.  These "orphaned" items looked to be old members from testing, previous loads etc.  It is possible that the members were removed from the Default hierarchy via a deletion from the dimension in Perspectives. (Still need to check if this causes the member to be deleted from the default but kept in Leaves).

I created some MDX to go through members in Leaves and not in the Default hierarchy, and delete them.
This cleaned up the orphaned/ unused members and the two hierarchies seem more aligned.

After a save data, I copied over the Product dimension and the hierarchies from the Product}hiers to Production.
So far so good - PAfE giving DIMIX values where alias is used, TM1Web returning reports with values, not just a blank structure.

Still not sure what happened here or how to prevent it from happening again but would be happy if anyone has anything to add.

------------------------------
George Tonkin