COGNOiSe.com - The IBM Cognos Community

Legacy Business Intelligence => COGNOS ReportNet => Report Studio => Topic started by: Ian Leslie on 29 Jul 2015 05:32:49 AM

Title: Report Studio Search Function
Post by: Ian Leslie on 29 Jul 2015 05:32:49 AM
Hi,

When doing a search using the Member Search with 'Contains any of these keywords' and 'Case Insensitive' and 'search all descendants listed' selected I enter a known keyword, in this instance 'weatherproof' and the results returned are the elements that match but not the level 1 description needed.

Any ideas as to why this might be happening.

Cheers,
Ian
Title: Re: Report Studio Search Function
Post by: bdbits on 29 Jul 2015 09:51:00 AM
First thing to check - view the result set from the query behind the prompt and see if in fact that value is in any of the rows.

If it is dimensional, is it a cube and are there any known facts associated with that dimensional member? If not, it might be getting dropped from the cube.
Title: Re: Report Studio Search Function
Post by: Ian Leslie on 30 Jul 2015 04:03:00 AM
hi bdbits,

Thanks for the reply, not sure I'm understanding what your saying, I'm not using a prompt to search, it's when I'm using the search option by right clicking on the element or hierarchy or when there are more than 50 members and you get the search option to look for more members.

Regards,
Ian
Title: Re: Report Studio Search Function
Post by: bdbits on 30 Jul 2015 04:03:46 PM
I was a little off, but the idea of looking at the underlying data still applies. Depending on how the data was modeled and the tool in use (e.g. Transformer, Dynamic cubes, etc), members can get excluded from a level especially if there are no associated facts. Since this appears to be a dimensional data source, it might be easiest to ask whoever created the package for you to validate that the desired member(s) have associated facts.

Otherwise, if it is not a data issue, I am not sure. Searching as you described definitely works here (10.2.1.1 FP4).
Title: Re: Report Studio Search Function
Post by: Ian Leslie on 04 Aug 2015 05:43:57 AM
Hi,

I've now raised it with IBM support who have confirmed it's a product defect, subject to an APAR.

Thanks

Ian