Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Planning Analytics
Created by Guest
Created on Oct 7, 2021

Name of the macro-enabled .xslm websheet needs correction in .blob file

With the older versions (which would connect to TM1 via PMHUB), the websheet names were same in .blob as well as .xlsm. However, any of the new versions that use the ODATA connection from PA for Excel to connect to TM1, has been displaying GUID name. As a result of this, it is difficult to relate the websheet names in the }Externals folder without having to open the related .blob file from }Applications folder and then comparing the 50 digit alpha-numeric file name. In absence of this, the developers will now have to perform additional tasks during deployment of code promotions to Prod and have to manually open some 150+ websheets in order to verify them.

In addition, we are also not able to use a utility (using VB Script) that we've been using in the past which helped us clean up the }Externals folder (by removing duplicate websheets), updating cell references etc.

Needed By Month
  • Admin
    Stuart King
    Nov 2, 2021

    We have never documented the contents of files, or patterns for file names (other than extension) in TM1. This is not something we plan to start documenting as it's subject to change. The exact problem you are describing is why we do not disclose this infomration.

  • Guest
    Nov 2, 2021

    The request was not for TM1 to support VB scripts, its just one of the few issues caused by the recent change in the .xlsm file names.

    If is the tool is subject to changes in future versions for the way it stores/names the file structures then ensure it is documented in the release notes before you make it available to public for use.



  • Admin
    Stuart King
    Nov 2, 2021

    I have declined this enhancement request.

    We do not document the internal file structure or names of files in a TM1 local database. VB scripts that rely on specific file names, or file content, are not be supported. Note that the file structure and even access to files stored by the database is subject to change in future versions of TM1.