Methods for saving an Exploration View

Planning Analytics for Microsoft Excel provides you with several different methods to save your Exploration Views. You can choose the method that suits your needs the best.

There are three ways that you can save your Exploration Views or list views. The best method for your view or report depends on where they will be opened, what type of data they need to store, and how they will be viewed.

Table 1. Feature comparison of the save types.
  Content Store MDX view TM1 Server view
Save location of the view Planning Analytics Workspace Content Store TM1® Server TM1 Server
Can be referenced by TurboIntegrator scripts No Yes Yes
Can store alias information Yes Yes Yes
Can store subset information for slicer selection Yes Yes Yes
Can define static, set based or expression based set information by axis Yes Yes Yes
Can store calculations Yes Yes No
Can store headers Yes Yes No
Can define asymmetric axis Yes Yes No
Compatibility with Planning Analytics for Microsoft Excel Can open and save the view Can open and save the view Can open and save the view
Compatibility with Planning Analytics Workspace Can open and save the view Can only open the view Can only open the view
Compatibility with TM1 Web Not compatible with the view Not compatible with the view Can open and save the view
Important: Converting a TM1 server view (.vue) to an MDX view (.xbv) might impact existing TurboIntegrator processes that use the view as a data source. Although the converted view looks the same when it is displayed, it has some variations that affect how data are retrieved by a process. The biggest difference is that the TM1 server view can have title subsets, whereas the analogous part of an MDX view is the 'slicer' or 'WHERE' clause, which contains individual members rather than subsets. After converting a TM1 server view to an MDX view, any processes that use the view as a data source should be verified and, if necessary, modified.