If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Drill behaviour

Started by krunal, 29 May 2017 01:33:33 AM

Previous topic - Next topic

krunal

Hi,

i have cube based report
After migrating from 10.1 to 10.2.2 drill up and drill down not working and throwing error
i have done sorting on Zone wise and also have drill on zone wise, if i remove sorting then drill behavior is working fine, but if i use sorting then i am getting error

ERROR
__________
Invalid coercion from 'member' to 'string' for '[ZONE__0]' in 'case [ZONE__0] when 'NORTH' then 1 when 'EAST-A' then 2 when 'EAST-B' then 3 when 'WEST' then 4 when 'SOUTH-A' then 5 when 'SOUTH-B' then 6 end'.


Sorting Condition
_________________
case ([BUSSINESS VIEW].[OTIF_TYPE].[ZONE]  )
when 'NORTH' then (1)
when 'EAST-A' then (2)
when 'EAST-B' then (3)
when 'WEST' then (4)
when 'SOUTH-A' then (5)
when 'SOUTH-B' then (6)
end

MFGF

Quote from: krunal on 29 May 2017 01:33:33 AM
Hi,

i have cube based report
After migrating from 10.1 to 10.2.2 drill up and drill down not working and throwing error
i have done sorting on Zone wise and also have drill on zone wise, if i remove sorting then drill behavior is working fine, but if i use sorting then i am getting error

ERROR
__________
Invalid coercion from 'member' to 'string' for '[ZONE__0]' in 'case [ZONE__0] when 'NORTH' then 1 when 'EAST-A' then 2 when 'EAST-B' then 3 when 'WEST' then 4 when 'SOUTH-A' then 5 when 'SOUTH-B' then 6 end'.


Sorting Condition
_________________
case ([BUSSINESS VIEW].[OTIF_TYPE].[ZONE]  )
when 'NORTH' then (1)
when 'EAST-A' then (2)
when 'EAST-B' then (3)
when 'WEST' then (4)
when 'SOUTH-A' then (5)
when 'SOUTH-B' then (6)
end

Hi,

10.1 was not very strict in its syntax parsing, and would allow you to use syntax that shouldn't really be legal. 10.2 onwards is more strict in its parsing and it has found an expression that should never have been permitted previously.

You say you are using a cube based report, but the three-part name you are citing [BUSINESS VIEW].[OTIF_TYPE].[ZONE] appears to be relational not dimensional? For a dimensional source I'd expect to see [BUSINESS VIEW].[Your Dimension].[Your Hierarchy].[Your Level] or similar. Are you sure you entered the complete item name?

Secondly, in a cube-based report, you are dealing with members rather than data items. Although something might appear as NORTH in your report, you are seeing the caption of the member, and under the covers the member is likely identified by a key which may be entirely different. You can obtain the caption of a member by using the caption() function or the roleValue() function, so I'd recommend you try using that here. The error you posted appears to be this exact issue - Cognos cannot figure out how to treat the members based on your expression comparing them with strings. Try extracting the captions and using these.

Cheers!

MF.
Meep!