IBM Support

What's coming next in IBM Planning Analytics 2.0.63 SC

News


Abstract

The following updates will be available in release 2.0.63 SC of Planning Analytics.

Content

Planning Analytics Workspace
The following new features are available in Planning Analytics Workspace.
 
User experience improvements
Numerous user experience improvements in the Planning Analytics Workspace 2.0.63 release signify our continued investment in design and usability.  Navigation, layout, and other improvements make it easier than ever to create models and analyze data.
You can learn all about the most recent improvements in this blog post
Rename a database in Planning Analytics Workspace (Cloud only)
Planning Analytics on Cloud customers can now rename a TM1 databases using Planning Analytics Workspace Administration. You no longer need to submit a support ticket to have a TM1 database renamed for you.

You must use the Planning Analytics Workspace new interface, which is also referred to as New Experience, to rename the database. This functionality is not available in the Planning Analytics Workspace Classic.
You must open a support request to rename a Cognos Controller Financial Analytics Publisher (FAP) databases. You cannot rename a FAP databases using Planning Analytics Workspace Administration.
Important: When you rename a database, any existing content that leverages or references the old database name will return errors that must be resolved manually.

The rename process affects a database in the following ways:

  • The database name is changed in the user interface.
  • The database directory in the prod directory is renamed with the new name.
  • The database name in the tm1s.cfg file is updated to match the new name.

  • Any ACL files provided by the customer are updated in our repo if it includes the folder that was just renamed.

  • If the directory rename cannot succeed, the whole process is canceled, any actions are reverted, and an error message is presented to the user.

To rename a database:
  1. Log on to Planning Analytics as an Administrator.
  2. On the Welcome page, click Administration.
  3. Click Databases.
  4. On the Databases panel, locate the database that you want to rename, and click its name.
  5. On the Details tab, check the database status. If the status is Started, click Stop.
    The database must be stopped before it can be renamed. It might take a few minutes to stop the database. When the process is complete, the database icon changes to indicate the status stopped database. You can now proceed with renaming the database.
  6. Next to the database name, click the Rename database icon rename icon.
    The current database name is highlighted.
  7. Overwrite the current database name with the new name, and click the Save (check mark) icon to proceed with rename process.
    The rename process might take several minutes to complete. When it's finished, the new database name is displayed in the Databases panel.
Remove a user without using IBM Subscriptions Manager (Cloud only)

Planning Analytics on Cloud administrators can remove users in Planning Analytics Workspace Administration without using IBM Subscriptions Management (SSM).

Administrators remove users only from the primary tenant (environment), and the system then removes the users from all secondary tenants (environments). The users are also automatically removed from SSM, from groups that they were members of, and from all environments that they were associated with. The removed users' personal assets are moved to a new folder named Unknown , but their shared assets remain in the shared folder.


 
Edit MDX source for a cube view
You can use the new MDX button on the toolbar to view and edit the MDX source for a cube view.
view mdx source
Use the new Box Plot visualization
You can use box plot visualizations to identify outliers and compare distributions in your data.

You can create a box plot to show the median, quartiles, and outlier and extreme values for a variable. The inter-quartile range is the difference between the 75th and 25th percentiles and corresponds to the length of the box. The middle line is the 50th percentile.

Above and under each box, 'whiskers' give additional information about the spread of the data.

Far out values are represent by adding "o" signs beyond the whiskers.

The mean score in a box plot is presented by a "+" sign.

Use the Key field in a box plot visualization to determine the items for which you want to identify outliers and compare distributions. 

This box plot example shows the gross profit statistics for various markets.
box plot visualization

Planning Analytics for Excel
The following compatibility announcement is important for Planning Analytics for Excel users.
Note: If you are upgrading from Planning Analytics for Microsoft Excel version 2.0.62 to Planning Analytics for Microsoft Excel version 2.0.63, you must uninstall Planning Analytics for Microsoft Excel version 2.0.62 before upgrading.
Create new Exploration View or Quick Report using a common view specification (CVS)

You can now use the CreateFromCVS API method to generate a new Exploration View or Quick Report using a common view specification (CVS).

A common view specification is JSON that is composed of two major parts; the MDX query and a sidecar for additional state information. Data driven mechanisms, such as TurboIntegrator, are only concerned with the MDX query. However, user interfaces will also consume the sidecar to ensure presentation consistency. 

For more information, see CreateFromCVS (Exploration View) and CreateFromCVS (Quick Report).

To learn more about Common View Specifications, see Common View Specification.

Conformance compatibility update

Planning Analytics for Microsoft Excel 2.0.63 contains conformance updates fundamental to improving the overall product experience, including the installation and post-installation experience. 

The 2.0.63 update of Planning Analytics for Microsoft Excel is not compatible with the current release of Cognos Office Connection. Users that use both Planning Analytics for Microsoft Excel and Cognos Office Connection are affected in their ability to upgrade to the latest release of Planning Analytics for Microsoft Excel. 

Users who utilize either Cognos Office Connection or Planning Analytics for Microsoft Excel on their own can continue using the latest releases of each. Users who utilize both Planning Analytics for Microsoft Excel and Cognos Office Connection for their reporting needs can continue using Planning Analytics for Microsoft Excel 2.0.62 alongside the latest release of Cognos Office Connection.

In an upcoming release, the Planning Analytics add-in will be converted from an installer-based delivery to a single file a fraction of the size. This will provide easier self service in enabling and disabling the add-in. Shortly following this upcoming release, Cognos Office Connection will enable the link between the two products once again. 

TM1 Web 
The following new features are available in TM1 Web.
 
Retrieve data from multiple TM1 databases in a websheet
You can now retrieve data from more than one TM1 database in a websheet. Limitations to this ability that were present in previous releases have been removed.

Planning Analytics SC 2.0.62 introduced the ability to retrieve data from multiple TM1 databases in a websheet, but imposed two limitations:
  • all databases referenced in a websheet had to be registered on the same Admin host
  • you could use multiple TM1 databases in a websheet only on Planning Analytics Local
These limitations have been removed. A websheet can now reference databases that are registered on different Admin hosts. You can also retrieve data from multiple TM1 databases in a websheet on both Planning Analytics Workspace Local and Planning Analytics on Cloud.
 
Note that you can retrieve data from multiple databases only in Custom Reports and Dynamic Reports, which use the VIEW function to retrieve data.

To successfully reference multiple databases in a websheet:
  • Database names must be static; computed database names are not supported.
  • All databases must be configured to use the same authentication mode.
  • Users must have common credentials across databases.
If one of the referenced databases is not running or a connection cannot be established, you will see an error in the websheet.
authentication error

[{"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":"a8m0z000000Gn0QAAS","label":"General"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
30 April 2021

UID

ibm16441053