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

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Needs more information
Workspace Planning Analytics
Created by Guest
Created on Nov 29, 2022

Application and plan deployment

Currently has been added the possibility to migrated with lifecycle manage the applications and plan across environments.

What is not possible is to migrate the application across multiple TM1 servers

For example, with the workbooks we can select source and target server and all the views/books are updated targeting to the selected new Tm1 server.

With appliacations and plan this is not possible.

Ideally we should clone the application, all the books inserted in the application must be cloned and the new application must point to the cloned books ones.

In order to do that we must avoid to deploy first in the personal folders but allow to deploy directly in the main folder (also becasue passing via personal folders is causing issues with the security)

Needed By Month
  • Guest
    Nov 30, 2022

    Hi Stuart

    yes you are right, would be alredy great to be able to rename when deploying.

    What we were not able to do is to migrate the application with the books working.

    During migration from one environemnt to another , even if the asset and the links exists in the target environment the migration is not able to point to the right assets and we are receiving error.

    So we are not able in fact to migrate nor betwen environments or instances (but i got your point on the instances) - i will probably open a case as seems probably a bug more then an enahcement

  • Admin
    Stuart King
    Nov 29, 2022

    I'm not sure this enhancement requested is valid.

    Plans and Applications are not associated with a specific TM1 database. Only the books and views used in Plans and Applications will be associated to a TM1 database. When you deploy a snapshot with a Plan or Application, the books and views in the Plan or Application will be imported into a folder that is created in the root of the public folder (this folder is created during deployment). The books and views can be remapped at this point, just like normal LCM. The newly deployed plan will point to the books and views in the folder that was created (which may have been remapped).

    Let me know if I'm missing something. I did a quick test to validate my above comments.

    I think it would be nice to have the ability to rename a Plan or Application on deployment. This would allows Plans and Applications to be duplicated with the assets being both duplicated and remapped to different databases.