Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only

  • 1.  Error when using Dataset as a fact table

    Posted Fri May 22, 2020 10:30 AM
    I'm having issues with a datamodule which consist of a dataset joined to 2 other tables.These 2 other tables come from a data module with a dataserver as a source. So linked tables.

    When I use this datamodule and select only columns from the tables (used as dimension tables) and not the dataset (used as a fact table)
    then an error occurs:
    XQE-GEN-0005 Found an internal error: java.lang.NullPointerException
    RSV-SRV-0042 Trace back:

    It looks like Cognos does not automatically uses the dataset (fact table) to join the tables. Because when I also add a column from the dataset, the correct data appears.

    When I add another fact table and select only columns from the (dimension) table then the error message below occurs:
    XQE-PLN-0229 This query is not supported, because it only contains dimension items and there is no single fact stream that covers all of the entities.
    The involved fact tables are: Query1_0, Query1_0_1. Resolve this issue by adding one or more fact items to the query.

    This is an issue for me, because I have this error in a dashboard with this datamodule. When I select a value from the first table, the error occurs for the second table, because Cognos wants to filter.
    I can do some workaround to use a table for the dimensions and add a local filter with fact data, but this only works when using a table, not with a filter added to the canvas.

    Can someone confirm this behaviour and maybe knows a workaround?

    ------------------------------
    Thomas van der Meer
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Error when using Dataset as a fact table

    Posted Sun May 24, 2020 07:37 PM

    I think there's two issues here.

    The first is the inconsistent error.  I think that you possibly should get the XQE-PLN-0229 error for the case where your module's fact table is a data set.   It is a reasonably clear message.  As a result I've logged a defect requesting consistency.

    The second issue is, should a query require a fact to be included in the report in order to work or should it be possible to get the query to find a relationship between the two query subjects through any of the fact query subjects to which they are conformed. I have not been able to think of a business case where such a query would come into play.  Could you explain what you are trying to achieve.



    ------------------------------
    IAN HENDERSON
    ------------------------------

    Original Message


  • 3.  RE: Error when using Dataset as a fact table

    Posted Mon May 25, 2020 05:07 AM
    What I'm trying to achieve is to join a dataset to multiple tables from an existing datamodule.
    This existing datamodule consists of tables from a dataserver connection with relations. It is the datamodule version of the Framework Manager model.
    In my case I created a datamodule with a complex (passthrough) query. The result is a set of rows with a couple of measures per month and profitcentercode. For performance reasons I created a dataset from this datamodule.
    And in the final datamodule I joined this dataset to the existing datamodule. Resulting in:
    Organisation <== 1:n ==> Dataset <== n:1 ==> Period
    Where organisation and Period are the linked tables from the existing datamodule.
    The same issue would apply when a user has uploaded an Excel file and joined this to the existing module.

    If I for example use organisation and period as filters and the dataset as the result table then this error occurs when selecting a value from the organisation or period.
    I hope I my explanation helps you to understand what I am trying to achieve.

    ------------------------------
    Thomas van der Meer
    ------------------------------

    Original Message


  • 4.  RE: Error when using Dataset as a fact table

    Posted Thu June 04, 2020 02:50 PM
    Hi Thomas, based on the info you've shared I don't see any reason for an error.  Can you share any details of the error message to help us figure out what the problem is? Are you able to submit an IBM Support case for this problem so we formally track the resolution of this problem? Feel free to email me at jason.tavoularis@ca.ibm.com

    ------------------------------
    Jason Tavoularis
    ------------------------------

    Original Message


  • 5.  RE: Error when using Dataset as a fact table

    Posted Mon June 08, 2020 08:15 AM
    Hi Jason. Thank you for you interest in this issue I am having.
    Important to know that I'm using Cognos 11.1.2.

    I finally found out what was causing this strange error. The null pointer exception was caused by an incorrect specified column dependency in one of the tables from the data module using the dataserver connection. The lowest level was defined as 'Repeating'. When I changed this to 'Unique', the problem was gone.

    ------------------------------
    Thomas van der Meer
    ------------------------------

    Original Message


Related Content