Planning Analytics

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?

I too am curious about this as we use the TM1Web API extensively, in our case by constructing a dynamic URL in another application that takes the user to the applicable websheet and sets the title element. Both the target websheet and the title element are dynamically constructed in the URL. I do not know of another mechanism to accomplish that currently other the TM1Web API. 

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?

Hi Grischa,

Websheets (Excel on the web) is an important part of IBM Planning Analytics.  We will continue to enhance the capabilities of websheets and the scalability of the service that supports websheets.

Although TM1Web is still a part of IBM Planning Analytics on-premise (including the newer 2.1 release) and Planning Analytics on Cloud, we are not making additional investments specifically in the TM1Web user interface.  Note that TM1Web is more than just websheets, it also includes it's own cube viewer, a navigation tree, and it's own web API as you already mentioned).   

In the Planning Analytics SaaS offering (not the same as Planning Analytics on Cloud) we do not provide the TM1Web user interface.  Websheets can still be used, but only be through books in Planning Analytics Workspace.  The product team does have a roadmap to improve the presentation of websheets in Planning Analytics Workspace.  Workspace does have a URL API that can be used to access books, the cube viewer widget, and Websheets.

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?

Hi Grischa,

Websheets (Excel on the web) is an important part of IBM Planning Analytics.  We will continue to enhance the capabilities of websheets and the scalability of the service that supports websheets.

Although TM1Web is still a part of IBM Planning Analytics on-premise (including the newer 2.1 release) and Planning Analytics on Cloud, we are not making additional investments specifically in the TM1Web user interface.  Note that TM1Web is more than just websheets, it also includes it's own cube viewer, a navigation tree, and it's own web API as you already mentioned).   

In the Planning Analytics SaaS offering (not the same as Planning Analytics on Cloud) we do not provide the TM1Web user interface.  Websheets can still be used, but only be through books in Planning Analytics Workspace.  The product team does have a roadmap to improve the presentation of websheets in Planning Analytics Workspace.  Workspace does have a URL API that can be used to access books, the cube viewer widget, and Websheets.

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?

Stuart

One of the benefits (And also downside) of TM1Web is that everything is there available for the user without a need for additional authoring of a user interface.  Given how many pre-defined cube views are often set up per cube it can be almost impossible to create an equivalent PAW  interface. One thing that would help would be for the PAW cube viewer to have an (optional) view selection as exists in the Architect/Perspectives cube viewer. When I saw optional, this would be something that could be controlled by the PAW author.  Given MDX in the viewer can be modified would it be that hard to provide this if  restricted to MDX views?  

John

Hi Grischa,

Websheets (Excel on the web) is an important part of IBM Planning Analytics.  We will continue to enhance the capabilities of websheets and the scalability of the service that supports websheets.

Although TM1Web is still a part of IBM Planning Analytics on-premise (including the newer 2.1 release) and Planning Analytics on Cloud, we are not making additional investments specifically in the TM1Web user interface.  Note that TM1Web is more than just websheets, it also includes it's own cube viewer, a navigation tree, and it's own web API as you already mentioned).   

In the Planning Analytics SaaS offering (not the same as Planning Analytics on Cloud) we do not provide the TM1Web user interface.  Websheets can still be used, but only be through books in Planning Analytics Workspace.  The product team does have a roadmap to improve the presentation of websheets in Planning Analytics Workspace.  Workspace does have a URL API that can be used to access books, the cube viewer widget, and Websheets.

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?

Hi John,

We like this suggestion.  There have been a few other requests for the same feature.  I think this should be an 'always on' feature in the cube viewer in the modeling workbench and an optional feature (enable\disable in the properties panel) in books.

One question, do you want to switch both the cube and view?  Or just select from views in the same cube? 

It might be worth pointing out that you can drag a view from the database tree over top of an existing cube view widget in a Workspace book.  This will prompt the book author with this:

We are thinking about exposing shortcuts to views in the Websheets (Applications folder in TM1Web) node in the database tree in Workspace books.  TM1Web displays these view shortcuts and they are helpful to organize commonly used views.  In Workspace books we could use the view shortcuts as another way to add views from TM1 to a book.  We are building a feature to manage (create, delete, rename, set public\private) view shortcuts in the PAW modeling workbench. 

Stuart

One of the benefits (And also downside) of TM1Web is that everything is there available for the user without a need for additional authoring of a user interface.  Given how many pre-defined cube views are often set up per cube it can be almost impossible to create an equivalent PAW  interface. One thing that would help would be for the PAW cube viewer to have an (optional) view selection as exists in the Architect/Perspectives cube viewer. When I saw optional, this would be something that could be controlled by the PAW author.  Given MDX in the viewer can be modified would it be that hard to provide this if  restricted to MDX views?  

John

Hi Grischa,

Websheets (Excel on the web) is an important part of IBM Planning Analytics.  We will continue to enhance the capabilities of websheets and the scalability of the service that supports websheets.

Although TM1Web is still a part of IBM Planning Analytics on-premise (including the newer 2.1 release) and Planning Analytics on Cloud, we are not making additional investments specifically in the TM1Web user interface.  Note that TM1Web is more than just websheets, it also includes it's own cube viewer, a navigation tree, and it's own web API as you already mentioned).   

In the Planning Analytics SaaS offering (not the same as Planning Analytics on Cloud) we do not provide the TM1Web user interface.  Websheets can still be used, but only be through books in Planning Analytics Workspace.  The product team does have a roadmap to improve the presentation of websheets in Planning Analytics Workspace.  Workspace does have a URL API that can be used to access books, the cube viewer widget, and Websheets.

Dear all,

I am currently helping a customer to move from a Rich-Tier-based (TM1-Web, TM1-Applications, etc.) application to the current version of PAW, TM1 Spreadsheet Service and PAfE. While migrating most of the TM1-Web-based functionality I am wondering if it is worth-while to still follow the "old-school" path of creating an application based around the navigation-tree of TM1-Web or if there is also a foreseeable end-of-life of the TM1-Web as we know it today - meaning it might also deprecate and spreadsheets in the future might only be visible inside of PAW and thus the navigation tree and the TM1-Web-URL-API would deprecate.

Does anyone have and idea or even insight on this and may lead me in the proper direction?