Cognos Analytics

 View Only

  • 1.  Query "Does Not Reference"...but it DOES!

    Posted Fri January 31, 2020 02:52 PM
    Edited by System Fri January 20, 2023 04:34 PM
    ​Hello - Anyone familiar with what might cause this?
    I have a report with about a dozen queries. Some queries are used as the source for other queries,
    so Query_A might be the source for Query_B. When I validate the report I get this warning:
    XQE-WRN-0076 Query "Query_B" references query "Query_A" but does not reference any of its data item."

    But it does! I can see in the query display that every data item in Query_B comes from Query_A, except a few calculations within Query_B.
    More than half the data items in Query_B have expressions like [Query_A].[DataItem].
    So why the warning?

    I know I can ignore the warning, but that just means the next person to crack this code open will try to figure out what they warning, too..

    Thanks for your insights and suggestions.


    ------------------------------
    Regards,
    Opher
    ------------------------------
    #CognosAnalyticswithWatson


  • 2.  RE: Query "Does Not Reference"...but it DOES!

    Posted Tue February 04, 2020 12:14 PM
    usually a query reference like this will require that you include some "join", typically via a detail filter, that connects that two queries.  it is strange, though, because typically this would result in a cross-join ERROR message, not a warning.  Are you able to look at the properties of your Query_B and see if there are any "governor" type properties where you could disable this warning?

    ------------------------------
    Albert Valdez
    albert@intelalytics.com
    ------------------------------

    Original Message


  • 3.  RE: Query "Does Not Reference"...but it DOES!

    Posted Tue February 04, 2020 05:47 PM
      |   view attached
    Hello @Albert Valdez - I'm not doing a join. I'm doing a query reference. it's the Cognos method of creating sub-queries, so that the output of one query becomes the input to another. This is covered in the Report Studio User Guide as Child queries. In my example (attached), Query ​A is the Parent query and B is the Child query.
    If I opened Query B all of it's objects have expressions in the format [A].[Column] - which is the query reference. Yet I get a warning that there is no reference.
    I know of no Governor settings that would impact these references.
    Thanks for your suggestions.

    ------------------------------
    Regards,
    Opher
    ------------------------------

    Original Message


  • 4.  RE: Query "Does Not Reference"...but it DOES!

    Posted Thu February 06, 2020 09:11 AM
    This behavior is not expected. Please submit an IBM Support case so it can be investigated.  To make it easier to investigate, try to simplify the scenario down to the simplest (fewest items) possible that still recreates the same problem.

    Enabling the same problem to be reproduced here at IBM is the goal here so if you can reproduce against our samples that would be ideal.

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

    Original Message


  • 5.  RE: Query "Does Not Reference"...but it DOES!

    Posted Thu February 06, 2020 12:52 PM
      |   view attached
    Hello @Jason Tavoularis - I have been trying to reproduce and cannot. It's possible the report is "corrupted" somehow, but only these warnings appear (see attached).
    The report is too complicated to re-build and I'd like to find a way to clear the warnings.
    I tried exporting the XML and re-importing it, hoping the process would flush the problem, but it did not change anything.
    Rachel Su said something during the AMA about Master-Detail relationships, which caught my attention because one of the warnings is also about Master-Detail ​issues. However, as far as I can determine, the report is not using a Master-Detail relationship.
    Any suggestions would be helpful. Company policy prevents me from sharing the report XML.
    Thanks.

    ------------------------------
    Regards,
    Opher
    ------------------------------

    Original Message


  • 6.  RE: Query "Does Not Reference"...but it DOES!

    Posted Thu February 06, 2020 01:34 PM
    @Opher Banarie - this is a long shot, but maybe try setting a master-detail reference up in the report?​

    ------------------------------
    Albert Valdez
    albert@intelalytics.com
    ------------------------------

    Original Message


  • 7.  RE: Query "Does Not Reference"...but it DOES!

    Posted Fri February 07, 2020 01:43 PM
    Can you copy queries in new report and do tabular data on final query?   If that gives error, it is some data item within it rather than looking on layout.

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

    Original Message


  • 8.  RE: Query "Does Not Reference"...but it DOES!

    Posted Fri February 07, 2020 04:29 PM

    Hello @Buddhi Gupta - Excellent suggestion!
    YES! Copying the two queries to another report clears the warning.
    What does that mean in practice, and how do I leverage that towards a solution?

    I don't know yet.
    But thanks for the idea.
    ​



    ------------------------------
    Regards,
    Opher
    ------------------------------

    Original Message


  • 9.  RE: Query "Does Not Reference"...but it DOES!

    Posted Mon February 10, 2020 09:40 AM
    Thanks for trying it. I would suggest to add each layout component from original report one by one in new report and test the report to identify which part is generating warning. 


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

    Original Message