Cognos Analytics

Cognos Analytics

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


#Product
#Analytics
#CognosAnalytics
#Analyticstools
#TechXchange Partner
#TechXchange Session
#TechXchange Presenter
#AI
 View Only

  • 1.  Link Breaking in Child Data Module for new objects

    Posted 09/23/20 11:18 AM

    Hi All,

     

    When first time I make a Data Module source of Child Data Module, it brings all content and have link reference to source Data Module. However, when I add new object/query in Source Data Module and try to add it to child Module, it is copied as independent object instead of having link to source.

     

    To keep all as linked objects, I have to reimport all again and do all calculations again.  This is time consuming and rework involved for any such changes in source during development phase.

     

    Is there any work around to add links for newly added objects in Source data Module?

     

    Thanks for inputs!

     

    Regards,

    Buddhi

     


    #CognosAnalyticswithWatson


  • 2.  RE: Link Breaking in Child Data Module for new objects

    Posted 09/23/20 04:04 PM
    Edited by System Admin 01/20/23 04:48 PM
      |   view attached

    The attached video is my attempt to replicate what I think you are trying to say what you've done.  Please review it and clarify the actions you are actually performing.  You will probably need to click on the view attached button.

    You mention calculations.  Are the objects you are complaining about stand alone calculations in your source module?   They don't get treated as references in the destination module.  They will be editable. 



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



  • 3.  RE: Link Breaking in Child Data Module for new objects

    Posted 09/28/20 01:31 PM
    Hi @IAN HENDERSON, Thanks for responding to this issue.

    I tried different types of objects and it's happing SQL based Objects.

    1. In Source module, create SQL based Object
    2. in Child Module, ​​bring objects from Source Module. They appear correctly as linked objects and can't modify it's properties
    3. Now add new SQL based object in Source Module. Changed attributes to some data items to be identifier instead of Measure.
    4. In Child Module, when try to import only this new SQL Object, it doesn't come as Linked Object and its properties can be updated and doesn't carry properties set in Source Modules. 

    I am using CA 11.1.6. 

    Please advise if this is an issue with SQL based Objects.

    Secondly calculations done on Linked Objects appear outside of Linked Object and  is confusing which one is source when using in Explorations.

    Thanks for any inputs!





    ------------------------------
    Buddhi Gupta
    ------------------------------

    Original Message


  • 4.  RE: Link Breaking in Child Data Module for new objects

    Posted 09/29/20 03:17 AM
    Hi Buddhi,

    I was able to simulate your issue in CA 11.1.7 as well. I can confirm this seems to be only the case when trying to link a 2nd sql object into the master(child) data module. It works however correctly for normal tables. Testing further by linking a view gave me the same problem of sql object: it is imported in stead of linked. See below picture: PROD_SQL was the original object, Cust_sql_2nd was the 2nd object I added afterwards , Customerinfo is a regular table that I could import as linked object and finally Customerinfo_view is the final object that again appears as a copy

    I will log this as a bug because behavior is inconsistent: creating a new master datamodule and linking it in completely will show all objects as linked as per below image:

    as a work around for now, you can eventually create separate data modules for each new object you need to add. I have tested changes in the existing sqls and these are all taken over correctly

    Hope this helps

    Peter


    ------------------------------
    Peter D'Haeyer
    ------------------------------

    Original Message


  • 5.  RE: Link Breaking in Child Data Module for new objects

    Posted 09/29/20 01:17 PM
    I couldn't find an existing defect (which doesn't mean that none exists, just that I could not find it) so I've logged one.

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

    Original Message


  • 6.  RE: Link Breaking in Child Data Module for new objects

    Posted 09/29/20 05:01 PM
    Thanks a lot Peter and Ian to testing and confirming the issue.

    As work around, I have to keep adding Whole data Module and remove unnecessary objects since creating Data module for each new objects will defeat purpose of maintaining one source for all child Data Modules.

    Hope it is resolved soon in next FP for 11.1.7.

    ------------------------------
    Buddhi Gupta
    ------------------------------

    Original Message


Related Content