IBM Support

Differences TM1 and Planning Analytics interface in Cognos Analytics 11.0.6+

Troubleshooting


Problem

With Cognos Analytics 11.0.6 a new datasource connection type has been introduced for Planning Analytics Server. This document will list the known differences between connecting through the TM1 datasource connection type and connecting through the Planning Analytics datasource conection type.

Environment

IBM Cognos Analytics 11.0.6+

Resolving The Problem

This document will list the known differences between connecting through the TM1 datasource connection type and connecting through the Planning Analytics datasource conection type.

The Member Unique Name will change when Planning Analytics is selected as datasource connection type

    • TM1 connection will generate a Member Unique Name containing [TM]. Example: [SalesCube].[region].[region]->:[TM].[region].[region].[World]
    • Planning Analytics connections will generate a Member Unique Name containing [TMR]. Example: [SalesCube].[region].[region]->:[TMR].[region].[region].[World]

    This can have the following implications:
      • Explicit Member Unique Names referenced or calculated in a report do not produce the expected results
      • Default values of prompt controls in reports do not produce the expected results
      • Saved parameter values in the report or schedule properties do not produce the expected results
The execution of a report with Planning Analytics datasource connection type, matches the execution of a report with TM1 datasource connection type in Dynamic Query Mode with qsUseNativeTM1Engine = true set.

    This can have the following implications:
    • additional information on qsUseNativeTM1Engine
    • each MDX will be generated with NON EMPTY, thus null suppression is applied on every MDX.
    • the null suppression will have an effect on rules (underfed or overfed)
    • the null suppression will have an effect on aggregations, ie. with weigh 0
    • the null suppression will have an effect on numeric attributes that are 0. This can be solved by setting UNDEFVALS; in the rules of the Attribute cube.
Report executions with Planning Analytics as datasource connection type do not require a Planning Analytics client to be installed.

The connection will be established through TM1 REST.

Automatic translation of elements is no longer mapped using Alias attributes during the publish process when using a Planning Analytics datasource connection type, but is done automatically using the new Localization features in Planning Analytics.

This can cause different results for translated element names, depending on the execution language, as well as different results when using the caption function in reports or when using filters on captions.
Planning Analytics hierarchies are supported as of Cognos Analytics 11.0.6 using the new Planning Analytics datasource connection type
Text Measures are supported as of Cognos Analytics 11.0.7 using the new Planning Analytics datasource connection type Subsets are supported as of Cognos Analytics 11.0.9 using using the new Planning Analytics datasource connection type

[{"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Report Authoring v11x","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0.9;11.0.8;11.0.7;11.0.6","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2018

UID

swg22014362

Page Feedback