IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Improve Data Transfer between Different TM1 Servers

TM1 does not a user friendly and easy mechanism to transfer data between different TM1 servers. Currently there are 2 options, but none of them can be properly used:

1 - Use Replication to transfer and synchronize data from different TM1 servers: This option is not useful if data is not manually entered in TM1 and recorded via transaction logs. If source data is calculated via rules and consolidations, then it does not work. If source data is transferred to TM1 cube via TI process without logging, then it does not work. Therefore this option is not useful in 90% of the cases.

2 - Using ODBO as data source in a TI process. This option is not user friendly at all because it works via MDX queries. It never worked for our requirements.

For clients who use TM1 for various purposes, for the sake of operation and for the sake of best performance, we use separate TM1 servers for different applications or solutions. For example, budgeting application can be in a different TM1 server than operational reporting application. There may be various reasons to have different TM1 server for different TM1 applications.

In such cases, we usually need to transfer data from one TM1 server to another TM1 server. For example, we may need to transfer high level budget figures to an operation reporting application to support some budget figures in reports. On the other hand we may need to transfer summary of calculated actual figures from an operation reporting application to a budget application that lie in different TM1 server.

Currently we have to export data from a source TM1 server to a text file or to a database and then ready it by destination TM1 server from the exported location. This makes it more difficult and time consuming to develop, as the current built in options in TM1 does not provide a proper solution to this common requirement.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 7 2020
  • Future consideration
Why is it useful?
Who would benefit from this IDEA? All TM1 clients who use multiple TM1 application that needs to work in integration to each other.
How should it work?

As a solution to this problem:

a new feature can be added in either of the following 2 options:

1 - Add an option to replication/synchronization definition in a way not use transaction log files but read the source cube itself when doing the synchronization every time. Moreover replication feature should also have the capability to read source cube views that are calculated via rules or dimension consolidations so that a high level summary of a source cube can be transferred to a target cube with less dimensions.

2 - In a TI process, when using IBM Cognos TM1 as data source, it should allow, not only using the cubes in the same TM1 server, but it should also allow connecting to a different TM1 server and using its cubes in the same way. In this option, it should allow using existing cubes views or subsets in source TM1 server.

This feature will make our lives easier as TM1 Developers and consultants. Regards,

Idea Priority High
Priority Justification It should be simple and straightforward to transfer data between different TM1 server instances to simplify sharing data in different TM1 applications.
Customer Name All Clients
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    11 Jun 06:46

    Creating the source TM1 Server/Instance as a datasource is so important. It is resulting in a lot of TI code and batch code to move data between our systems. A simple datasource would be such a big improvement.

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions