IBM Support

Custom Report does not refresh correctly in IBM Planning Analytics for Excel

Troubleshooting


Problem

In certain cases, the Custom Report is not refreshing correctly and does not return any values.

Cause

Invalid or inaccessible metadata represented in Planning Analytics for Excel reports lead to performance degradation and potential validation issues. This is because the client must perform a fallback validation on the report's metadata before it renders the result. We recommend proper model administration, including appropriate user privileges for reports and workbooks.

As of Planning Analytics for Excel 2.0.68, an alternate metadata validation algorithm for Custom Reports is now the default. While this validator provides overall performance improvement, for certain use cases performance might be better with the older validator. You can disable the new validator in the tm1features.json.

Resolving The Problem

If your Custom Report does not refresh or a refresh does not return values, you can disable the new validator in tm1features.json:

  1. Close all Microsoft Office applications.
  2. Navigate to the C:\<user profile path>\Cognos\Office Connection folder. For example:
    C:\Users\[userID]\AppData\Local\Cognos\Office Connection
  3. Open the tm1features.json file in a text editor. (If a tm1features.json file does not exist, then create one using Notepad, ensuring that it is saved with the file extension .json and not .txt.)
  4. Set the "r68_DisableNewCRValidator" parameter to "true". The revised parameter looks like this:
    {"r68_DisableNewCRValidator": true}
  5. Save the tm1features.json file.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD29G","label":"IBM Planning Analytics"},"ARM Category":[{"code":"a8m3p0000008uD4AAI","label":"PAfE"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
10 January 2022

UID

ibm16497179