10.2.1 Defects - Workspace

The below are against 10.2.1 DMR model using DQM mode.

For most of the defects the report has a crosstab with prompts on the report page to dynamically select rows and measures and a period tree prompt to select the period columns. The report has drills enabled.

Again, will update defect numbers as we get them. But that seems to be a time consuming process and am not the one involved.

Drill through lost on drill down

Drills not synched between chart and crosstab - Drill down on Product, Quarter combination in chart does not get reflected in crosstab

Drill on measures not synched between chart and crosstab - Drill down on fact cell intersection on chart does not reflect correctly in crosstab

Drill up and re-prompt doesn’t get reflected - Drill up on first run of the report and reset dimension. New dimension does not get reflected in objects

Resetting prompted widgets will re-prompt and then selecting different prompt values does not have any effect on the widgets.

Drill up/down and drill through doesn't pass all context values to the drill through report.

Charts - Drill and prompt on the same hierarchy does not reflect once drills are enacted - If a prompt dimension is used as series or categories then once a drill is acted upon the series/category re-prompting does not have any effect.

Drills get enabled and disabled intermittently on categories/rows and series/columns - Initially chart, crosstab do not have drills enabled on the time period series as set up in the report. Once drills are executed on the fact cells or on the chart intersections the drills become enabled on the time series.

Cognos 10.2.1 DQM DMR Defects - Part 2

Drill and Re select Dimension with Render Variable - Behaves differently if measure is based on data item vs measure based on prompt macro.

If 2 members are defined - one with a token prompt macro and another with an MDX expression defined on top of the first data item. If member sets are defined on the 2 members and drill behvaiour set for the first member to replace expression and the second expression to preserve. Drill up/down on one dimension and then resetting dimension and then drilling up/down does not work.

Prompt Macro and MDX Expressions - topCount with token prompt macro

Not all MDX expressions work on prompt macro. topCount does not work on a data item that has #prompt(,'token')#.

Prompt Macro and MDX Expressions - roleValue with MUN prompt macro

Not all MDX expressions work on prompt macro. roleValue does not work on a data item that has #prompt(,'memberUniqueName')#.

Periods to Date does not work as expected with any expression in the 2nd argument in CQM mode.

It has to be a member for the right result to be returned. Even if the expression returns a member, PTD does not work correctly and returns only one period. This is only in CQM mode.

I will list out a couple of Workspace defects in the next article.

10.2.1 DQM DMR Defects - Part 1

This is going to be quite a long list so am listing out only a few important ones and most of them relate to prompt macros and drills. These are all against 10.2.1 DMR model using DQM mode. I am  not going to explain in detail with images unless someone wants me to since there are too many. I will update the article with Defect Numbers as we receive them.

For most of the defects the report has a crosstab with prompts on the report page to dynamically select rows and measures and a period tree prompt to select the columns. The report has drills enabled.

Level Label Calculation does not work as expected when using prompt macro and drills.

When we use a data item with a prompt macro for crosstab rows to dynamically select the dimension, have drill enabled and have a query item to get Level Label using the prompt macro data item the level label does not get captured consistently.

When we switch between dimensions in the prompt and then drill up/down the level label data item does not get reflected.

To disable member and data cache at report level for testing, query is set to use DB only and Use Local Cache is set to no. This causes charts to work incorrectly.

Report has a period tree prompt with chart and crosstab displaying periods selected in the prompt. With Use Local Cache set to No, selection of periods in the tree prompt returns "No Data Available" message.

Prompt Macros with Data Item names in Value Prompts do not work

If the value prompt Use Value is set to a Data Item name rather than a level then drilling up on one of the dimensions and then re-setting the dimension prompt to another dimension does not have any effect.

Prompt Macros with Filter Calculations in Value Prompts do not work

Same as above except if the use value is set to include a filter expression then re-setting dimension does not work.

Drill and Prompt on same hierarchy - Drill up returns to selections made rather than following dimensional hierarchy.

Select 2012, Q1 2012, Q1 2013 and run report. Drill down on 2012. Drill up on Q1 2012 takes you back to 2012, Q1 2012, Q1 2013 instead of showing list of years which is confusing to the users.

Optimized Master Detail relationships with DQM, not really

Here's an extract from IBM site on optimized master detail relationship using DQM (http://publib.boulder.ibm.com/infocenter/cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.dyn_query.10.1.0.1.doc%2Fc_master-detail.html):

Optimized master detail relationships in reports

Master detail relationships allow you to deliver information that would otherwise require two or more reports.

You specify a relationship between the query in the master data container and the query in the detail data container. For example, you can combine a master list with a detail chart. The list can contain product lines and the chart can show details for each product line.

With the dynamic query mode, master detail relationships are optimized. IBM® Cognos® pushes the master query as a separate edge to the detail query. Therefore, instead of sending one detail query to the data source for each master value, only one query is sent for HTML, PDF, and Microsoft Excel spreadsheet software output formats.
That is not the case though when you check the profile tree logs. Master detail relationships, still execute the old fashioned way with DQM. I had this confirmed by IBM as well that this is as per design.
I am posting this so developers don't get misleaded by the article. Wish IBM removes the misleading article.