Planning Analytics

 View Only

  • 1.  Migration issue with view formats in PAfE, TM1Web and PAW

    Posted 4 days ago
    Edited by Grischa Rehmer 3 days ago

    Dear all,

    my current customer has used view-formats heavily in the past with Architect, Perspectives and TM1-Web, due to the possibility to use different formats for the same dimensionelements.

    By "view-formats" I mean the formats that the cube-viewer allows you to directly store to a cube-view into the 375 ID in the view-file.

    Our initial hope was that PAfE and PAW would just be able to use the legacy-formats when opening the views. But this unfortunately is not the case.

    So our second approach was to open the views in PAfE, set the formats in the cube-viewer in PAfE and be able to retrieve that format the next time a view gets opened in PAfE or TM1-Web. It seems like the format is not stored whether one uses a native or an MDX view.

    Is there something on the road-map regarding legacy compatibility of this functionality?



    ------------------------------
    Grischa Rehmer
    ------------------------------



  • 2.  RE: Migration issue with view formats in PAfE, TM1Web and PAW

    Posted 3 days ago

    Hi Grischa,

    I love it that you even specify the internal property ID of the format property of a view;-! And I'm with you on that expectation that IF a format is defined for a native view, exposed in the REST API as the FormatString property of the NativeView entity, that that format should become the default format for the view when displayed.

    To set expectations though, as is, there is no such property build in for MDX views but, MDXView entity type being an open type (read: one can specify additional properties for individual instances), one could also add a property 'FormatString' with an MDXView as well and give it the same meaning.

    I know there is a lot going on wrt formatting in PA at the moment but I'll leave it to one of the PMs to respond to your road-map question;-!



    ------------------------------
    Hubert Heijkers
    STSM, Program Director TM1 Functional Database Technology and OData Evangelist
    ------------------------------

    Original Message


  • 3.  RE: Migration issue with view formats in PAfE, TM1Web and PAW

    Posted 2 days ago

    Hi Grischa,

    When working in Excel (PAfE) sheets the formatting is really just Excel formatting.  In this case the format infomration is stored as part of the xlsx\xlsm file.

    When working in Workspace (PAW) we have format options on the cube viewer that can be saved to the PAW content store.  Note that cube views can be saved independently of the PAW books.  There are a many formatting features being added to the PAW cube viewer this year.  Make sure to take a look at the new features in the upcoming PAW 2.0.101 release in February.  The view formatting infomration is saved as part of the PAW view instead of the original view object in the TM1 database.

    We are not planning on reading and interpreting any of the previous formats that might have been saved along with the views in TM1.  The older format options provide very few formatting options compared to the modern PAW cube viewer.  We are planning on exposing the more power formatting features from the PAW cube viewer in PAfE (using the PAW cube viewer in PAfE) as part of the 2025 roadmap.  

     



    ------------------------------
    Stuart King
    Product Manager
    IBM Planning Analytics
    ------------------------------

    Original Message


  • 4.  RE: Migration issue with view formats in PAfE, TM1Web and PAW

    Posted an hour ago
    Edited by Grischa Rehmer an hour ago

    Dear Hubert, dear Stuart,

    first of all, thanks a lot for providing your detailed answers. I am happy that we can reach out directly to you guys.

    So, if I get this right, the current situation is, that no tool except Architect/Perspectives (resp. Arc or Notepad) is designed to be able to change or display the format of a native view.

    I am note sure how many users actually use the functionality of view-specific formats. This customer has a truck-load of these views and uses them in a TM1-web based FP&A application.

    This means, until they have moved everything from TM1-web to PAW for V3.1 and use PAW-explorations in conjunction with PAW-spreadsheets, they need to continue to use Architect to maintain these views, because PAfE and PAW will overwrite the 375 property in the vue-file. Maybe it would be a good idea to not erase the 375-property on views that get overwritten to at least stay backwards-compatible.



    ------------------------------
    Grischa Rehmer
    ------------------------------

    Original Message