Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson

There is no way to preserve a link between a Workspace MDX view and view stored in the TM1 Server.  Removing or changing the source view in the TM1 Server will not impact the view in Workspace in any way.  

Can I ask about the use case here?  Is this a view that is being generated or refreshed by a Ti process or in one of the other older TM1 clients?

I would like to point out that you can share views between Workspace and Planning Analytics for MS Excel now.  We are slowly moving towards Workspace being the primary content store for Planning Analytics.  Ideally, we would like to move other objects into Workspace such as subsets, UDCs, and Websheets.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------

Original Message:
Sent: Wed October 02, 2019 07:22 AM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson

Hello Stuart,
Thanks for answering.
I've got, at this time, no real use case but I was just trying to confirm what I was guessing.
The view I was mentioning was a view created by a Turbo Integrator Process.
We're trying to convert our Executive Views into PA (Workspace and/or Excel) views automatically with a script I wrote and it's going quite well as I'm able to reproduce the layout of the sourceview as well as almost all the calculation members.
My point was that, as I'm an old TM1 fellow, I had some difficulties to understand which kind of object these TM1 MDX views are: you can create them in Architect but you're not able to see it, when you're in PAW, the only way to access it is to put them on a book's sheet... It will take a little time for me to get familiar with this new environment ;-)
I'm also  a big fan and consumer of the TM1 Rest Api and as of today, except if I missed something, I didn't see much Api to "play" with PAW objects (Books, Views, Security Groups..)

------------------------------
Bob
------------------------------

Original Message:
Sent: Thu October 03, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

There is no way to preserve a link between a Workspace MDX view and view stored in the TM1 Server.  Removing or changing the source view in the TM1 Server will not impact the view in Workspace in any way.  

Can I ask about the use case here?  Is this a view that is being generated or refreshed by a Ti process or in one of the other older TM1 clients?

I would like to point out that you can share views between Workspace and Planning Analytics for MS Excel now.  We are slowly moving towards Workspace being the primary content store for Planning Analytics.  Ideally, we would like to move other objects into Workspace such as subsets, UDCs, and Websheets.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Wed October 02, 2019 07:22 AM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson

I agreed that an API for Workspace would be extremely helpful.  We are currently working on a URL API that will allow you to embed Workspace widgets into your own web applications (similar to the TM1Web URL API).  I'm hopeful that we can eventually extend this API to do things like refresh/rebuild Workspace views, add/remove users and groups, and manage security on Workspace content.

Something thing I really like about Workspace is it's ability for Analyst role users to create their own content (currently limited views and books) and control who that content is shared with.  I think this is much better than how TM1 content is has to be either public or private.  Moving content such as subsets and views to Workspace does present a some interest challenges that the Planning Analytics team is keen to work on.  One of the things I'm very interested in is how we can design views in Workspace and leverage those views as a data source for a Ti process.  Another interesting issue yet to be solved is how we will allow non-admin users to drag and drop data source files into Workspace book so the file may be uploaded to a view (probably with an existing Ti).

------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------

Original Message:
Sent: Thu October 03, 2019 03:21 PM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello Stuart,
Thanks for answering.
I've got, at this time, no real use case but I was just trying to confirm what I was guessing.
The view I was mentioning was a view created by a Turbo Integrator Process.
We're trying to convert our Executive Views into PA (Workspace and/or Excel) views automatically with a script I wrote and it's going quite well as I'm able to reproduce the layout of the sourceview as well as almost all the calculation members.
My point was that, as I'm an old TM1 fellow, I had some difficulties to understand which kind of object these TM1 MDX views are: you can create them in Architect but you're not able to see it, when you're in PAW, the only way to access it is to put them on a book's sheet... It will take a little time for me to get familiar with this new environment ;-)
I'm also  a big fan and consumer of the TM1 Rest Api and as of today, except if I missed something, I didn't see much Api to "play" with PAW objects (Books, Views, Security Groups..)

------------------------------
Bob

Original Message:
Sent: Thu October 03, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

There is no way to preserve a link between a Workspace MDX view and view stored in the TM1 Server.  Removing or changing the source view in the TM1 Server will not impact the view in Workspace in any way.  

Can I ask about the use case here?  Is this a view that is being generated or refreshed by a Ti process or in one of the other older TM1 clients?

I would like to point out that you can share views between Workspace and Planning Analytics for MS Excel now.  We are slowly moving towards Workspace being the primary content store for Planning Analytics.  Ideally, we would like to move other objects into Workspace such as subsets, UDCs, and Websheets.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Wed October 02, 2019 07:22 AM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson

Stuart,

While I certainly believe there is some value in allowing external apps leverage the widgets in PAW, I think there is even more value in allowing widgets to be created that can be incorporated into PAW.  

The URL api that is being built would require you to build the entire application infrastructure so that you can embed a few widgets from PAW.   That is a lot of work, and for some companies, that may be what they are looking for.    However, if you allow a developer to create a widget that can be embedded into PAW, then the only development needed is that additional widget.   It would already leverage the PAW infrastructure and the end users could incorporate those widgets into new dashboards without requiring a whole application to be developed externally.

To me, leveraging PAW (rather than circumventing it) is where there is much more value.


------------------------------
Steven Garno
------------------------------

Original Message:
Sent: Fri October 04, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

I agreed that an API for Workspace would be extremely helpful.  We are currently working on a URL API that will allow you to embed Workspace widgets into your own web applications (similar to the TM1Web URL API).  I'm hopeful that we can eventually extend this API to do things like refresh/rebuild Workspace views, add/remove users and groups, and manage security on Workspace content.

Something thing I really like about Workspace is it's ability for Analyst role users to create their own content (currently limited views and books) and control who that content is shared with.  I think this is much better than how TM1 content is has to be either public or private.  Moving content such as subsets and views to Workspace does present a some interest challenges that the Planning Analytics team is keen to work on.  One of the things I'm very interested in is how we can design views in Workspace and leverage those views as a data source for a Ti process.  Another interesting issue yet to be solved is how we will allow non-admin users to drag and drop data source files into Workspace book so the file may be uploaded to a view (probably with an existing Ti).

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Thu October 03, 2019 03:21 PM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello Stuart,
Thanks for answering.
I've got, at this time, no real use case but I was just trying to confirm what I was guessing.
The view I was mentioning was a view created by a Turbo Integrator Process.
We're trying to convert our Executive Views into PA (Workspace and/or Excel) views automatically with a script I wrote and it's going quite well as I'm able to reproduce the layout of the sourceview as well as almost all the calculation members.
My point was that, as I'm an old TM1 fellow, I had some difficulties to understand which kind of object these TM1 MDX views are: you can create them in Architect but you're not able to see it, when you're in PAW, the only way to access it is to put them on a book's sheet... It will take a little time for me to get familiar with this new environment ;-)
I'm also  a big fan and consumer of the TM1 Rest Api and as of today, except if I missed something, I didn't see much Api to "play" with PAW objects (Books, Views, Security Groups..)

------------------------------
Bob

Original Message:
Sent: Thu October 03, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

There is no way to preserve a link between a Workspace MDX view and view stored in the TM1 Server.  Removing or changing the source view in the TM1 Server will not impact the view in Workspace in any way.  

Can I ask about the use case here?  Is this a view that is being generated or refreshed by a Ti process or in one of the other older TM1 clients?

I would like to point out that you can share views between Workspace and Planning Analytics for MS Excel now.  We are slowly moving towards Workspace being the primary content store for Planning Analytics.  Ideally, we would like to move other objects into Workspace such as subsets, UDCs, and Websheets.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Wed October 02, 2019 07:22 AM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson

I agree with Steve. There is a lot to be learned from the adoption/failed adoption of the tm1 web url api. Many actions require complex development (in the case of tm1web  involving dojo). Trying to extend the functionality was hard to say the least. Finally, you had to continually fight with CORS issues. It seems that a PAW platform that's more open to extension/augmentation would be better.

------------------------------
Ryan Clapp
------------------------------

Original Message:
Sent: Mon October 07, 2019 10:08 AM
From: Steven Garno
Subject: TM1 MDX views in PAW sheet

Stuart,

While I certainly believe there is some value in allowing external apps leverage the widgets in PAW, I think there is even more value in allowing widgets to be created that can be incorporated into PAW.  

The URL api that is being built would require you to build the entire application infrastructure so that you can embed a few widgets from PAW.   That is a lot of work, and for some companies, that may be what they are looking for.    However, if you allow a developer to create a widget that can be embedded into PAW, then the only development needed is that additional widget.   It would already leverage the PAW infrastructure and the end users could incorporate those widgets into new dashboards without requiring a whole application to be developed externally.

To me, leveraging PAW (rather than circumventing it) is where there is much more value.


------------------------------
Steven Garno

Original Message:
Sent: Fri October 04, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

I agreed that an API for Workspace would be extremely helpful.  We are currently working on a URL API that will allow you to embed Workspace widgets into your own web applications (similar to the TM1Web URL API).  I'm hopeful that we can eventually extend this API to do things like refresh/rebuild Workspace views, add/remove users and groups, and manage security on Workspace content.

Something thing I really like about Workspace is it's ability for Analyst role users to create their own content (currently limited views and books) and control who that content is shared with.  I think this is much better than how TM1 content is has to be either public or private.  Moving content such as subsets and views to Workspace does present a some interest challenges that the Planning Analytics team is keen to work on.  One of the things I'm very interested in is how we can design views in Workspace and leverage those views as a data source for a Ti process.  Another interesting issue yet to be solved is how we will allow non-admin users to drag and drop data source files into Workspace book so the file may be uploaded to a view (probably with an existing Ti).

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Thu October 03, 2019 03:21 PM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello Stuart,
Thanks for answering.
I've got, at this time, no real use case but I was just trying to confirm what I was guessing.
The view I was mentioning was a view created by a Turbo Integrator Process.
We're trying to convert our Executive Views into PA (Workspace and/or Excel) views automatically with a script I wrote and it's going quite well as I'm able to reproduce the layout of the sourceview as well as almost all the calculation members.
My point was that, as I'm an old TM1 fellow, I had some difficulties to understand which kind of object these TM1 MDX views are: you can create them in Architect but you're not able to see it, when you're in PAW, the only way to access it is to put them on a book's sheet... It will take a little time for me to get familiar with this new environment ;-)
I'm also  a big fan and consumer of the TM1 Rest Api and as of today, except if I missed something, I didn't see much Api to "play" with PAW objects (Books, Views, Security Groups..)

------------------------------
Bob

Original Message:
Sent: Thu October 03, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

There is no way to preserve a link between a Workspace MDX view and view stored in the TM1 Server.  Removing or changing the source view in the TM1 Server will not impact the view in Workspace in any way.  

Can I ask about the use case here?  Is this a view that is being generated or refreshed by a Ti process or in one of the other older TM1 clients?

I would like to point out that you can share views between Workspace and Planning Analytics for MS Excel now.  We are slowly moving towards Workspace being the primary content store for Planning Analytics.  Ideally, we would like to move other objects into Workspace such as subsets, UDCs, and Websheets.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Wed October 02, 2019 07:22 AM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson

Steven and Ryan, I will share this feedback with the rest of the Planning Analytics team.


------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------

Original Message:
Sent: Tue October 08, 2019 02:25 AM
From: Ryan Clapp
Subject: TM1 MDX views in PAW sheet

I agree with Steve. There is a lot to be learned from the adoption/failed adoption of the tm1 web url api. Many actions require complex development (in the case of tm1web  involving dojo). Trying to extend the functionality was hard to say the least. Finally, you had to continually fight with CORS issues. It seems that a PAW platform that's more open to extension/augmentation would be better.

------------------------------
Ryan Clapp

Original Message:
Sent: Mon October 07, 2019 10:08 AM
From: Steven Garno
Subject: TM1 MDX views in PAW sheet

Stuart,

While I certainly believe there is some value in allowing external apps leverage the widgets in PAW, I think there is even more value in allowing widgets to be created that can be incorporated into PAW.  

The URL api that is being built would require you to build the entire application infrastructure so that you can embed a few widgets from PAW.   That is a lot of work, and for some companies, that may be what they are looking for.    However, if you allow a developer to create a widget that can be embedded into PAW, then the only development needed is that additional widget.   It would already leverage the PAW infrastructure and the end users could incorporate those widgets into new dashboards without requiring a whole application to be developed externally.

To me, leveraging PAW (rather than circumventing it) is where there is much more value.


------------------------------
Steven Garno

Original Message:
Sent: Fri October 04, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

I agreed that an API for Workspace would be extremely helpful.  We are currently working on a URL API that will allow you to embed Workspace widgets into your own web applications (similar to the TM1Web URL API).  I'm hopeful that we can eventually extend this API to do things like refresh/rebuild Workspace views, add/remove users and groups, and manage security on Workspace content.

Something thing I really like about Workspace is it's ability for Analyst role users to create their own content (currently limited views and books) and control who that content is shared with.  I think this is much better than how TM1 content is has to be either public or private.  Moving content such as subsets and views to Workspace does present a some interest challenges that the Planning Analytics team is keen to work on.  One of the things I'm very interested in is how we can design views in Workspace and leverage those views as a data source for a Ti process.  Another interesting issue yet to be solved is how we will allow non-admin users to drag and drop data source files into Workspace book so the file may be uploaded to a view (probably with an existing Ti).

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Thu October 03, 2019 03:21 PM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello Stuart,
Thanks for answering.
I've got, at this time, no real use case but I was just trying to confirm what I was guessing.
The view I was mentioning was a view created by a Turbo Integrator Process.
We're trying to convert our Executive Views into PA (Workspace and/or Excel) views automatically with a script I wrote and it's going quite well as I'm able to reproduce the layout of the sourceview as well as almost all the calculation members.
My point was that, as I'm an old TM1 fellow, I had some difficulties to understand which kind of object these TM1 MDX views are: you can create them in Architect but you're not able to see it, when you're in PAW, the only way to access it is to put them on a book's sheet... It will take a little time for me to get familiar with this new environment ;-)
I'm also  a big fan and consumer of the TM1 Rest Api and as of today, except if I missed something, I didn't see much Api to "play" with PAW objects (Books, Views, Security Groups..)

------------------------------
Bob

Original Message:
Sent: Thu October 03, 2019 07:39 AM
From: STUART KING
Subject: TM1 MDX views in PAW sheet

There is no way to preserve a link between a Workspace MDX view and view stored in the TM1 Server.  Removing or changing the source view in the TM1 Server will not impact the view in Workspace in any way.  

Can I ask about the use case here?  Is this a view that is being generated or refreshed by a Ti process or in one of the other older TM1 clients?

I would like to point out that you can share views between Workspace and Planning Analytics for MS Excel now.  We are slowly moving towards Workspace being the primary content store for Planning Analytics.  Ideally, we would like to move other objects into Workspace such as subsets, UDCs, and Websheets.

------------------------------
Stuart King
IBM Planning Analytics Offering Manager

Original Message:
Sent: Wed October 02, 2019 07:22 AM
From: Robert MILLI
Subject: TM1 MDX views in PAW sheet

Hello,
When you insert a TM1 MDX view in a PAW Sheet, you could remove the TM1 MDX view and the PAW Sheet will continue to work.
So I think that PAW doesn't keep track of the TM1 source view which has been used.
Am I right ?
Is there a way to preserve this "link", meaning if you update the view it will update the Sheet ?

------------------------------
Regards,
Bob
------------------------------

#PlanningAnalyticswithWatson