COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Report Studio => Topic started by: cbochner on 09 Oct 2013 11:41:53 AM

Title: At least one invalid member reference was encountered in the query
Post by: cbochner on 09 Oct 2013 11:41:53 AM
Hello.I have a report running off a cube and I get an error message of: At least one invalid member reference was encountered in the query.'[Attendance & Vacation Cube].[Date].[Date].[Day]->:[PC].[@MEMBER].[20131005]'. The problem is that 20131005 has no data since were not open on Staurday's so when i select a date range STARTING with that date, I get this error message. Is there a way out? Please Assist.
Thank You,

Chaim Bochner
Title: Re: At least one invalid member reference was encountered in the query
Post by: gurralakrishna on 10 Oct 2013 08:48:53 AM
Hello,

the issue is the date used as member were changed mean cube regenerated.
Can you please provide more details like where are you opening the report?
In report studio or work space advance?

Regards,
Krishna
Title: Re: At least one invalid member reference was encountered in the query
Post by: cbochner on 10 Oct 2013 09:55:15 AM
Thanks for the quick reply.

I'm using Report Studio against dimensional data from the cube.  On the prompt page there are two date prompts.  When i select a date starting from a Saturday, I get the error message.  My understanding is that there are no members for Saturday in our cube.

Please Reply,

Thank You.
Title: Re: At least one invalid member reference was encountered in the query
Post by: bdbits on 10 Oct 2013 02:06:13 PM
Are your date prompts derived from your date dimension? A cube will normally only include dimension members that tie to one or more measures/facts. So as long as the prompts are based off of the dimension, you should not be able to select invalid dates.

If the problem is because the dates are tied to some facts but not others, you probably need to modify the expression you are using (is it in a slicer?). If this is the case, it would be useful to attach the report spec here. We can then open it in RS and take a look and possibly suggest an alternate expression.