The hierarchy already belongs to the projected hierarchy list

5. RE: The hierarchy already belongs to the projected hierarchy list

Like

Vivien

Posted Mon June 20, 2022 03:56 AM

Hi,

Thank again for your help

yes I did remove until I find where the error was. Anyway it was my colleague to solve this.
We have this 2 data item :

[data item A]
tuple ([data item B], [data item C], [data item D])

[data item B]
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
)

We need to had properties to the member function :
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
, 'unique name' , 'caption' , [The].[Hierarchy]
)

regards,
Vivien

------------------------------
Vivien
------------------------------

Original Message

6. RE: The hierarchy already belongs to the projected hierarchy list

Like

IBM Champion

Paul Mendelson

Posted Mon June 20, 2022 07:31 AM

The MDX parser really doesn't like if statements like that.

Instead try this:

#case prompt('param','token')
when 1 then '[data item E]'
else '[data item F]'
end
#

Glad to hear you got it though!

------------------------------
Paul Mendelson
------------------------------

Original Message

Original Message:
Sent: Mon June 20, 2022 03:56 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi,

Thank again for your help

yes I did remove until I find where the error was. Anyway it was my colleague to solve this.
We have this 2 data item :

[data item A]
tuple ([data item B], [data item C], [data item D])

[data item B]
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
)

We need to had properties to the member function :
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
, 'unique name' , 'caption' , [The].[Hierarchy]
)

regards,
Vivien

------------------------------
Vivien

Original Message:
Sent: Sat June 18, 2022 06:13 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

Let's try this. Cut down the report so it's only the one crosstab, then start deleting items from it until you have the minimum object that is still causing the issue. It may be possible that a combination of items causes it, so deleting one or the other resolves it.

Once you have that, post the xml here and I'll go over it.

My next guess is there's an expression that isn't fully valid in mdx. Check for aggregate summaries where you have a comma separated series of values. Like: total([measure] within set [item1],[item2])

Also look for calculated members that do not explicitly reference a hierarchy.

DQM no longer supports "override dimensional information", are you using that anywhere?

------------------------------
Paul Mendelson

Original Message:
Sent: Fri June 17, 2022 03:19 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi Paul,

Thank you for your reply.

I have no detail filters
I have 2 slicers, but none of them are used in the crosstab.
No local joins or unions in the query explorer

thank you again, I still search what the cause could be on my side.
Hope I could give you a feedback.

Regards,

------------------------------
Vivien

Original Message:
Sent: Thu June 16, 2022 09:43 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

I've done a few upgrade projects, and DQM is far less forgiving of query design issues than CQM.

In the report you're running, check the queries. Do you have detail filters or slicers? Do you have items in your data container from the same hierarchies that you're filtering or slicing on? Do you have any local joins or unions in the query explorer?

------------------------------
Paul Mendelson

Original Message:
Sent: Thu June 16, 2022 02:34 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi team,

I'm in a migration from 10.2.2 (CQM SSAS 2012) to 11.2.2 (DQM SSAS 2019) and when I run a report on 11.2.2 version I get this error :

XQE-MDX-0012 The hierarchy already belongs to the projected hierarchy list.

I'm not able to understand what does that means neither to find result on google which could guide me in how resolve the issue.

Is there anyone who could give me a hint ?
many thanks,

------------------------------
Vivien
------------------------------

#CognosAnalyticswithWatson

7. RE: The hierarchy already belongs to the projected hierarchy list

Like

Vivien

Posted Tue June 21, 2022 02:37 PM

Sorry for the delay, I move on others errors.
To give you a reply. Here what it return :

XQE-V5-0017
V5 syntax error found for data item 'dtB' of query '01 - R9005 ACTUAL - Income Statement', invalid token "" found after "[dtF]".

It's quite odd because I checked formula multiple time but the error still raise.
Thank you again for your time.

------------------------------
Vivien
------------------------------

Original Message

Original Message:
Sent: Mon June 20, 2022 07:30 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

The MDX parser really doesn't like if statements like that.

Instead try this:

#case prompt('param','token')when 1 then '[data item E]'else '[data item F]'end#

Glad to hear you got it though!

------------------------------
Paul Mendelson

Original Message:
Sent: Mon June 20, 2022 03:56 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi,

Thank again for your help

yes I did remove until I find where the error was. Anyway it was my colleague to solve this.
We have this 2 data item :

[data item A]
tuple ([data item B], [data item C], [data item D])

[data item B]
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
)

We need to had properties to the member function :
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
, 'unique name' , 'caption' , [The].[Hierarchy]
)

regards,
Vivien

------------------------------
Vivien

Original Message:
Sent: Sat June 18, 2022 06:13 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

Let's try this. Cut down the report so it's only the one crosstab, then start deleting items from it until you have the minimum object that is still causing the issue. It may be possible that a combination of items causes it, so deleting one or the other resolves it.

Once you have that, post the xml here and I'll go over it.

My next guess is there's an expression that isn't fully valid in mdx. Check for aggregate summaries where you have a comma separated series of values. Like: total([measure] within set [item1],[item2])

Also look for calculated members that do not explicitly reference a hierarchy.

DQM no longer supports "override dimensional information", are you using that anywhere?

------------------------------
Paul Mendelson

Original Message:
Sent: Fri June 17, 2022 03:19 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi Paul,

Thank you for your reply.

I have no detail filters
I have 2 slicers, but none of them are used in the crosstab.
No local joins or unions in the query explorer

thank you again, I still search what the cause could be on my side.
Hope I could give you a feedback.

Regards,

------------------------------
Vivien

Original Message:
Sent: Thu June 16, 2022 09:43 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

I've done a few upgrade projects, and DQM is far less forgiving of query design issues than CQM.

In the report you're running, check the queries. Do you have detail filters or slicers? Do you have items in your data container from the same hierarchies that you're filtering or slicing on? Do you have any local joins or unions in the query explorer?

------------------------------
Paul Mendelson

Original Message:
Sent: Thu June 16, 2022 02:34 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi team,

I'm in a migration from 10.2.2 (CQM SSAS 2012) to 11.2.2 (DQM SSAS 2019) and when I run a report on 11.2.2 version I get this error :

XQE-MDX-0012 The hierarchy already belongs to the projected hierarchy list.

I'm not able to understand what does that means neither to find result on google which could guide me in how resolve the issue.

Is there anyone who could give me a hint ?
many thanks,

------------------------------
Vivien
------------------------------

#CognosAnalyticswithWatson

8. RE: The hierarchy already belongs to the projected hierarchy list

Like

IBM Champion

Paul Mendelson

Posted Wed June 22, 2022 01:39 PM

did you copy it from somewhere? I wonder if there's a non-breaking space that somehow snuck in. Try rewriting it from scratch.

------------------------------
Paul Mendelson
------------------------------

Original Message

Original Message:
Sent: Tue June 21, 2022 02:36 PM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Sorry for the delay, I move on others errors.
To give you a reply. Here what it return :

XQE-V5-0017
V5 syntax error found for data item 'dtB' of query '01 - R9005 ACTUAL - Income Statement', invalid token "" found after "[dtF]".

It's quite odd because I checked formula multiple time but the error still raise.
Thank you again for your time.

------------------------------
Vivien

Original Message:
Sent: Mon June 20, 2022 07:30 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

The MDX parser really doesn't like if statements like that.

Instead try this:

#case prompt('param','token')when 1 then '[data item E]'else '[data item F]'end#

Glad to hear you got it though!

------------------------------
Paul Mendelson

Original Message:
Sent: Mon June 20, 2022 03:56 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi,

Thank again for your help

yes I did remove until I find where the error was. Anyway it was my colleague to solve this.
We have this 2 data item :

[data item A]
tuple ([data item B], [data item C], [data item D])

[data item B]
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
)

We need to had properties to the member function :
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
, 'unique name' , 'caption' , [The].[Hierarchy]
)

regards,
Vivien

------------------------------
Vivien

Original Message:
Sent: Sat June 18, 2022 06:13 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

Let's try this. Cut down the report so it's only the one crosstab, then start deleting items from it until you have the minimum object that is still causing the issue. It may be possible that a combination of items causes it, so deleting one or the other resolves it.

Once you have that, post the xml here and I'll go over it.

My next guess is there's an expression that isn't fully valid in mdx. Check for aggregate summaries where you have a comma separated series of values. Like: total([measure] within set [item1],[item2])

Also look for calculated members that do not explicitly reference a hierarchy.

DQM no longer supports "override dimensional information", are you using that anywhere?

------------------------------
Paul Mendelson

Original Message:
Sent: Fri June 17, 2022 03:19 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi Paul,

Thank you for your reply.

I have no detail filters
I have 2 slicers, but none of them are used in the crosstab.
No local joins or unions in the query explorer

thank you again, I still search what the cause could be on my side.
Hope I could give you a feedback.

Regards,

------------------------------
Vivien

Original Message:
Sent: Thu June 16, 2022 09:43 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

I've done a few upgrade projects, and DQM is far less forgiving of query design issues than CQM.

In the report you're running, check the queries. Do you have detail filters or slicers? Do you have items in your data container from the same hierarchies that you're filtering or slicing on? Do you have any local joins or unions in the query explorer?

------------------------------
Paul Mendelson

Original Message:
Sent: Thu June 16, 2022 02:34 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi team,

I'm in a migration from 10.2.2 (CQM SSAS 2012) to 11.2.2 (DQM SSAS 2019) and when I run a report on 11.2.2 version I get this error :

XQE-MDX-0012 The hierarchy already belongs to the projected hierarchy list.

I'm not able to understand what does that means neither to find result on google which could guide me in how resolve the issue.

Is there anyone who could give me a hint ?
many thanks,

------------------------------
Vivien
------------------------------

#CognosAnalyticswithWatson

9. RE: The hierarchy already belongs to the projected hierarchy list

Like

Vivien

Posted Sat June 25, 2022 07:45 AM

Copy from your previous message.
When rewriting from scratch it's ok.
thanks

------------------------------
Vivien
------------------------------

Original Message

Original Message:
Sent: Wed June 22, 2022 01:38 PM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

did you copy it from somewhere? I wonder if there's a non-breaking space that somehow snuck in. Try rewriting it from scratch.

------------------------------
Paul Mendelson

Original Message:
Sent: Tue June 21, 2022 02:36 PM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Sorry for the delay, I move on others errors.
To give you a reply. Here what it return :

XQE-V5-0017
V5 syntax error found for data item 'dtB' of query '01 - R9005 ACTUAL - Income Statement', invalid token "" found after "[dtF]".

It's quite odd because I checked formula multiple time but the error still raise.
Thank you again for your time.

------------------------------
Vivien

Original Message:
Sent: Mon June 20, 2022 07:30 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

The MDX parser really doesn't like if statements like that.

Instead try this:

#case prompt('param','token')when 1 then '[data item E]'else '[data item F]'end#

Glad to hear you got it though!

------------------------------
Paul Mendelson

Original Message:
Sent: Mon June 20, 2022 03:56 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi,

Thank again for your help

yes I did remove until I find where the error was. Anyway it was my colleague to solve this.
We have this 2 data item :

[data item A]
tuple ([data item B], [data item C], [data item D])

[data item B]
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
)

We need to had properties to the member function :
member(
if(?param? = 1)
then ([data item E])
else ([data item F])
, 'unique name' , 'caption' , [The].[Hierarchy]
)

regards,
Vivien

------------------------------
Vivien

Original Message:
Sent: Sat June 18, 2022 06:13 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

Let's try this. Cut down the report so it's only the one crosstab, then start deleting items from it until you have the minimum object that is still causing the issue. It may be possible that a combination of items causes it, so deleting one or the other resolves it.

Once you have that, post the xml here and I'll go over it.

My next guess is there's an expression that isn't fully valid in mdx. Check for aggregate summaries where you have a comma separated series of values. Like: total([measure] within set [item1],[item2])

Also look for calculated members that do not explicitly reference a hierarchy.

DQM no longer supports "override dimensional information", are you using that anywhere?

------------------------------
Paul Mendelson

Original Message:
Sent: Fri June 17, 2022 03:19 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi Paul,

Thank you for your reply.

I have no detail filters
I have 2 slicers, but none of them are used in the crosstab.
No local joins or unions in the query explorer

thank you again, I still search what the cause could be on my side.
Hope I could give you a feedback.

Regards,

------------------------------
Vivien

Original Message:
Sent: Thu June 16, 2022 09:43 AM
From: Paul Mendelson
Subject: The hierarchy already belongs to the projected hierarchy list

I've done a few upgrade projects, and DQM is far less forgiving of query design issues than CQM.

In the report you're running, check the queries. Do you have detail filters or slicers? Do you have items in your data container from the same hierarchies that you're filtering or slicing on? Do you have any local joins or unions in the query explorer?

------------------------------
Paul Mendelson

Original Message:
Sent: Thu June 16, 2022 02:34 AM
From: Vivien
Subject: The hierarchy already belongs to the projected hierarchy list

Hi team,

I'm in a migration from 10.2.2 (CQM SSAS 2012) to 11.2.2 (DQM SSAS 2019) and when I run a report on 11.2.2 version I get this error :

XQE-MDX-0012 The hierarchy already belongs to the projected hierarchy list.

I'm not able to understand what does that means neither to find result on google which could guide me in how resolve the issue.

Is there anyone who could give me a hint ?
many thanks,

------------------------------
Vivien
------------------------------

#CognosAnalyticswithWatson

Cognos Analytics