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

Reports studio reports using cube packages

Started by bpsanoj, 17 Jun 2009 12:31:41 AM

Previous topic - Next topic

bpsanoj

Hi Friends, I need to create few reports in report studio using cube packages.Few complex filters are using in this report.I'm mainly facing issue while comparing the dates with our prompt date,current_date.(varchar and date mismatch errors).But this errors are resolved by using cast functions.The report vaildation shows no errors with few warnings.But when I run the reports,it throws the below error.

"PCA-ERR-0087 -The "crossJoinSet" operator is not applicable. The limit on the number of tuples per edge has been exceeded (-2)"

Our requirement is successfully done in report studio using FM packages (database package).But fails to build using cube package.Is there any real limitations when building complex reports from cube?

dlafrance

Problem i have seen with RS with cube :

Prompt calendar is hard to use with a cube (but there is a workaround that is a bit complex.)

You cannot do joins between queries based on the cube.

Sometimes you have to work with the member AND the category code to do what you need (ex filter)

mycognos

Is there any way to get the time dimensions in DATE format when using cube package? I am taking the values in date dimension directly from the database not from the date wizard, and when i bulid cube it is coming in varchar/string format not as date. In the cube source i have changed the type to date, still its not working.

Could you please explain why date promts and join conditions are not recommended in cubes...

bpsanoj

So u mean to say no joins can be used between queries when we use Cube package as the data source. I'm getting discrepancies while comparing calendar dates in a range to fetch a measure say,revenue. Data type mismatch (date/varchar) is the main issue I faced.

dlafrance


bpsanoj

Yah absolutely, I have tried time dimension conversions using cast data types but on validating i'm getting the warning as "The expression, is too complex for carrying over the attributes (format, currency and unit of measure). Column attributes are only retained for expressions with just 2-part item references.". And next time if use any additional cast function report will throw error "Cross-join error"   Plz help....