Cognos Analytics

Cognos Analytics

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

 View Only
  • 1.  Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Thu August 13, 2020 11:16 AM
    I have created a new Data Module that combines a Data Set with a Framework Manager Package.  The Data Set is joined to a table from the Framework Manager Package with an inner join.  The report is then sourced from the new Data Module.  It has both Required and Optional filters/prompts.  Prompts are selected from a prompt page.  However, when executing the report the filters that are set to Optional are behaving as if they are set to Required.  So, when executing the report the prompt page appears and the Finish button does not become active until all prompts are filled.  Whereas, the expected behavior is that only prompts who's filters are set to Required should need to be filled to set the Finish button to active.  Has anyone encountered this issue or advise on how to proceed?  
    Thanks

    ------------------------------
    Shawn Peronto
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Thu August 13, 2020 11:32 AM
    Haveing similar "issues" using prompt and promptmany macro in FM models as well as ?parameter? macro in report.

    Talked to IBM about "this" as well as the "prompt information" stored in FM model not being used in RS.

    Seems like 11.2.x might eventually respect the settings and how to offer and execute the filter dialogs from "interactive viewer".

    We filed several EHRs on this. Drop me a note if this is interesting.

    --
    Mit freundlichen Grüßen // Kind regards,

    Ralf Roeber


    --

    AMVARA Consulting S.L.

    Domicile and Court of Registry: Barcelona, No: 42979, Folio6, Hoja B416926,#1, Owner and Director: Ralf Röber

    AMVARA Consulting S.L., Gran Via de les Corts Catalanes 636, Princ. 1B, 08007 Barcelona / Spain

    Phone: +49-421-40896001, +49-711-89467029, +34-717 102 603

    info@amvara.de

    www.AMVARA.de







  • 3.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Thu August 13, 2020 08:32 PM
    It's a bug.

    If an object from the data set is used in the report in conjunction with an object from the FM package where there's an optional prompt the prompt will not be treated as optional. If the FM object with the optional prompt is used then the prompt is correctly treated as optional. I'll log that tomorrow morning.

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



  • 4.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Fri August 14, 2020 10:22 AM
    I can't see if the optional filter is from your FM package or if it's set in the report.
    If it's in the report only then it sounds like the prompt is set to requeried?
    For the prompt to be optional both the filter and the prompt should be set to optional.

    ------------------------------
    Jesper Bjerre
    ------------------------------



  • 5.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Fri August 14, 2020 10:45 AM
    The prompt and filter is set in the report.  The property is set to Optional for both the prompt and the filter.  The prompt and filter is against a query item from the Framework Manager package.   Prior to joining the data set to the Framework Manager Package, these prompts did behave as Optional as they should because that is their selected property for both the prompt and filter.  Then, upon creating the Data Module that joins the Data Set to the Framework Manager Package and then resourcing the report to use the Data Module, this un-edited prompt now behave as Required.

    ------------------------------
    Shawn Peronto
    ------------------------------



  • 6.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Fri August 14, 2020 11:15 AM
    Did you try creating a custom table with dataset and FM query and use on report with optional prompts? 

    I am creating Native sql with prompt macro to pass default values and join with other QS to achieve Optional Filter like behavior.

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



  • 7.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Fri August 14, 2020 03:47 PM
    I don't see custom tables as an option.  The client is on version 11.0.12.

    ------------------------------
    Shawn Peronto
    ------------------------------



  • 8.  RE: Optional Filters Act as Required When Data Sets Are Used in Data Module

    Posted Fri August 14, 2020 03:44 PM
    The work around: 
    In the prompt's properties add to the Static choices and the Default sections the value 'All'.   Next, in the query, there is the original data item that will be presented (leave that alone), add a copy of that data item and call it "Filter_XXX".  In the data item's expression definition add a concatenation function and prefix it with 'All'.  For example, CONCAT('All', Column1). 
    Next, edit the existing filter with the following: 
    SUBSTRING( [Filter_Column1], 1, 3 ) IN (?p_Prompt?)
    OR
    SUBSTRING( [Filter_Column1], 4 ) IN (?p_Prompt?)

    Not exactly the most efficient querying, but so far this is working.

    ------------------------------
    Shawn Peronto
    ------------------------------