I have a Date based hierarchy in my Transformer Cube.
The first level is Period which contains either 'WTD' or 'FUT' to indicate the period in which the day of the week occurs.
The second level is Day name SUNDAY, MONDAY, TUESDAY, etc....
When I build the cube each day, the current day of the week moves from the 'FUT' period to the 'WTD' period.
My report includes the 'WTD' level and then all the days of the week as column headers on my crosstab.
However, after building the Transformer Cube, when I try and run the report I get the following error.
OP-ERR-0181 - At least one invalid member reference was encountered in the query.'[Stockouts by Rank Band WTD TY/LY].[Date]. [Date].[Day Name]->:[PC].[@MEMBER].[TUESDAY]'
In the report, the properties of the TUESDAY member are:
Path [Stockouts by Rank Band WTD TY/LY].[Date].[Date].[Day Name]->:[PC].[@MEMBER].[TUESDAY~8513827]
Ref [Stockouts by Rank Band WTD TY/LY].[Date].[Date].[Day Name]->:[PC].[@MEMBER].[TUESDAY~8513827]
Member Caption TUESDAY
Member Unique Name [Stockouts by Rank Band WTD TY/LY].[Date].[Date].[Day Name]->:[PC].[@MEMBER].[TUESDAY~8513827]
Level Unique Name [Stockouts by Rank Band WTD TY/LY].[Date].[Date].[Day Name]
Hierarchy Unique Name [Stockouts by Rank Band WTD TY/LY].[Date].[Date]
Dimension Unique Name [Stockouts by Rank Band WTD TY/LY].[Date]
Level Number 2
Level Label [Date]..[Day Name 3]
Parent Unique Name [Stockouts by Rank Band WTD TY/LY].[Date].[Date].[Period]->:[PC].[@MEMBER].[WTD]
The build seems to be adding an integer (with a ~) on to the end of the current day.
The current day is the ONLY one affected!
Right now, the only way I know to resolve this is to change the report to include [TUESDAY~8513827] instead of [TUESDAY].
But, I will get the same error tomorrow for Wednesday.
Obviously, this is not a meaningful way to support this report.
Any thoughts would be greatly appreciated.
Thanks in advance,
Adam.
Hi,
In Transformer, all members (categories) in a dimension have to have a unique ID (category code). If Transformer finds a non-unique ID, it will make it unique by appending a ~ followed by a randomly generated number. The only way to prevent this is to force your category codes to be unique manually. Where else in the dimension is the TUESDAY category code being used? Could you concatenate it with another value to stop it from clashing with the ID of this member?
Regards,
MF.