SC99 release notes:

The list of new features are provided in the following link:

https://www.ibm.com/support/pages/node/7172963

The defects list is in the link below:

https://www.ibm.com/support/pages/node/6192099

 

A quick review of the key changes:

Key call outs in this release

  • Enhanced Action button search function

When selecting a TI Process for an Action Button, you can now type in the name of the process you want to use rather than having to search for it

  • Export  data from  a cube or view on the modelling workbench

You can now export data from a cube or view to a .csv file. The exported file is saved to your local Downloads directory.

To export data from a view, right-click the view on the modelling workbench Databases tree, then click Import/Export > Export data.

When you export data, you can set options that determine:

  • which hierarchy, set, and/or members to include in the export
  • a range of numeric or string values to include in the export
  • whether consolidated, rule-derived, or zero value are included in the export

          GQ comment – I found a simple view at leaf level exported without issue, but anything more complex, only the header was exported.

General Updates

There are no changes for Applications and Plans in this upgrade.

It is not unusual for the occasional change to go undocumented.  One such change is the exporting a cube view to Excel.

Now, when, you export a cube view to Excel the row structure is retained – previously the structure was removed

Changes in books and reporting

  • New Advanced synchronisation options on member change

Two new options, Member and leaves and Leaves, are now available for the member change events under Advanced synchronisation

The Advanced synchronisation feature allows you to customize how each hierarchy in the cube viewer or visualization displays when a synchronization event is received by that widget.

When a member change synchronization occurs, in addition to other options, you can now choose to display the member and its leaves or just the leaves in the widget that is receiving the synchronisation event

  • New Waterfall Visualisation

The new visualisation is called Waterfall.  The pre-existing waterfall has been renamed Legacy waterfall and is still available.

An example of a typical waterfall is shown below

The changes to the new Waterfall visualisation are as follows:

  • The Change the bar type asoption in the bar right-click menu.

Use this option to change the bar type to:

 Auto, Delta, Adjustment, or Subtotal.

  • The Accumulate totalsproperty under Visualisations > Data.

Use this property to correctly render values from multiple Total bars in the visualisation instead of changing the TM1 data.

If you want to use the new visualisation in existing views, you need to reopen the book and manually replace the legacy waterfall with the new waterfall.

  • Use action buttons to synchronise groups and hierarchies on navigation

With the new Advanced context feature in action buttons, you can now pass context and synchronize groups between books on navigation.

Widgets in the same group synchronize together. You can also select which hierarchies are used to pass context.

Previously, action buttons depended on the default synchronization group to provide context to the same synchronisation group in the target book.

With Advanced context, you can map a source synchronisation group to a target synchronisation group and select which of the hierarchies, common to both groups, receive context. You can also configure multiple action buttons to pass context to a single target book and drill through data easily.

The first step in using this new functionality is to  set up synchronization.  The widgets in both books need to be of the same synchronization group. Advanced context supports all three synchronization groups (Book, Sheet, and Custom).

The steps below show how to map the synchronisation groups and configure context passing:

  1. In edit mode, add an action button to the source book.
  2. Go to the action button’s Properties and under Navigation, enable Navigate to destination.
  3. Click Other bookand select a target book and the tab that you want to pass context to.
  4. Click Pass context.  The Advanced context link becomes available.
  5. Click Advanced context and select Custom group mapping.
  6. Note: The Default group mapping displays the default synchronisation groups and hierarchies. To edit or configure these settings, go to Custom group mapping.

  1. Select the source group which passes the context, the target group that receives the context, and the hierarchies you want to synchronise.
  • Rollback value changes in a view
    • Additional functionality to roll back data entry is now available in the Workbench.

The Rollback data entry button is located on the workbench toolbar and is activated once a value is added in the view

When the Roll Back button is clicked, a message confirming the rollback will appear at the top right of the screen.

  • Thumb cell formatting options for a view

The Format Manager now includes options to format the thumb cells in a view

 

The functionality is available in both the Row header and Column header sections

The options available:

  • Show Thumb– Use this option to hide or show the thumb cells.
  • Show Hierarchy– when selected, this will show the hierarchy name.  If an attribute is being displayed, the show hierarchy name needs to be selected to show the name of the attribute
  • Show icon – Use this option to show or hide the arrow icon in the thumb cell
  • Apply format – when switched on, the Thumb cells will be formatted the same as the Row or Column header

 

The example below shows the Row and Column headers are formatted; the Column Thumb is not shown, but the Row Thumbs are formatted the same as the Row and the Show Hierarchy button is selected.

  • Save a cube view as a native view

You can now save a cube view as a native view.

The Save to Server menu option under the Save button has been renamed to Save to database.

The Save to database dialog box now includes the Native option, which allows you to save an MDX view as a native TM1 view.

Note: When a view contains a calculation, it cannot be saved as a native view.

In the Name field, you can rename the view, or select another view from the drop-down menu, which shows names of other existing views.

If you select the Default checkbox, the Name input field is disabled, and the current view is selected as the default view.

  • Changed Selector Menu options

The menu options for adding a Selector widget have changed. They are now consistent in the Data tree, the cube viewer, and the Fields panel.

The previous options, Add as selector widget (Data tree) and Add widget as (cube viewer and Fields panel), are replaced by the following two options:

Add selector tile:  Use to add the selector widget as a tile. You can add 3 types of tiles:

                  Single tile, Multiple tiles, and Range selection tile.

 

          Add selector list: Use to add the selector widget as a list. You can add 3 types of lists:

                  Single list, Multiple lists, and Multiple selection lists.

The new menu options are available from the following context menus in the Data tree, the cube viewer, and the Fields panel:

  • Dimension context menu
  • Hierarchy context menu
  • Sets context menu

 

In the following example, the new menu options are shown from a dimension context menu on the Data tree:

Changes in modelling

  • Drive Explorer enhancements

When you are in a directory, you can see the number of items in that directory and the remaining disk space.

  • Inline notifications

The drive explorer now displays inline notifications about the status of actions you perform.

For example, when compressing files, an inline notification appears when the process is being performed and when it is complete.

  • Unzipping files

The process for unzipping files has improved. You can now expand a file into the directory you are viewing or into a folder.

To expand a file into the directory you are viewing, click Expand.

To expand a file into a folder, click Expand to, then name the folder, and click Create.

The contents of the unzipped file are in the newly created folder.

  • Overwrite notification when expanding a file

If you expand a file to an existing folder with the same name, the following notification appears:

You cannot choose which files are overwritten. The notification appears only once.

  • Tm1s log

     The tm1s.log file is now visible in the log directory. The file’s presence can be seen, but it cannot be opened or deleted.

  • Improved Performance

The drive explorer has improved performance when displaying a large number of files and folders.

  • Improved verification of valid file types on file upload

On file upload, Planning Analytics Workspace now determines the validity of a file based on the file type instead of the file extension.

Some of the file types that are supported include:

  • Text files (such as .txt, .csv, .css, .html)
  • Application files (such as .docx, .json, .ics, .xml, .php, .pdf, .zip, .7z, .rtf, .rar, .xlsm)
  • Image files (such as .jpeg, .jpg, .svg, .gif, .png, .heic)
  • Font files (such as .tff,. woff, .otf)
  • Video files (such as .mp4, .mpeg, .avi)
  • Audio files (such as .mp3, .wav, .weba, .mid)

 

    NOTE:  Some of the application flash screens may have changed as part of this exercise

  • Export a dimension or hierarchy from a modelling workbench

 

You can now export a dimension or a dimension hierarchy to a .csv file. The exported file is saved to your local Downloads directory.

To export, right-click a dimension or hierarchy on the modelling workbench Databases tree, then click Export members. 

You can also click the Export members icon  on the dimension editor to export a dimension.

When you export a dimension or hierarchy, the resulting .csv file includes the following information about each member:

  • name
  • parent/child relationship
  • type
  • weight
  • any defined attribute names and values

When they are exported, attribute names are prefixed with either ATTR_N or ATTR_S, depending on the attribute type (numeric or string, respectively).

 Changes in administration

  • Identify the HTTP port number for a Planning Analytics database (Cloud only)

You can now easily identify the HTTP port number for a database in Planning Analytics Administration.

To view the port number for a database:

      1. Open Planning Analytics Administration
      2. Click the Databases tile, then click a database name.

The port number is shown as the REST API Port on the Details tab.      

Request a Discussion