Another issue with Cognos:
Today I learnt a new caveat with Cognos Report Studio. I had a business case where I need to create two prompts, One cascading onto the other.
But the trick was that Cascading had to be conditional. For ex: for a particular value (let’s say ‘YYY’) of Prompt1, Prompt2 should display otherwise it should be blank. And to make it more complicated, Prompt1 was Multi-select.
I am no expert with Cognos so I started with my usual instincts and implemented the situation as:
1. Created Prompt1 with Multi-Select option.
2. Created Prompt2 without the cascade.
3. Add a filter to the Query of Prompt2: ?filter1? like ‘YYY’
1. Created Prompt1 with Multi-Select option.
2. Created Prompt2 without the cascade.
3. Add a filter to the Query of Prompt2: ?filter1? like ‘YYY’
Being a database guy, I thought that this should work and to a extent it did. Issue was that when I select ‘YYY’ as the first selection and rest of the values after that then it worked fine.
Now the problem arises when ‘YYY’ is not the first selection. Then second prompt remains blank.
I couldn’t understand that what was the reason. I changed filter to ?filter1? like ‘%YYY%’ but still no result.
Then I thought that Cognos might not treat Like as databases do. So I tried CONTAINS but still the same.
Then I checked IN function and it works like a charm. ‘YYY’ IN ?filter1?
It’s nothing great but just a minor issue which might spoil your Friday evenings.
Hope this helps.
I’ll try to find exact difference between “LIKE” and “CONTAINS”.
I F*CKING LOVE YOU - cognos is awful with multi-selects and 'contains' operators... but this trick works!
ReplyDelete