Planning Analytics

 View Only
  • 1.  xbf views and TurboIntegrator Issues

    Posted yesterday

    Hi All, 

    We've got pre-defined views that were set up in the Remote Desktop via Perspectives, and therefore they were .vue file type. 

    Over the month end some of our less experienced administrators changed the view through PAW to include new elements and then saved it to the server. This changed the file type to .xbf. 

    However, now when we try to run the processes they fail where ever there is a Viewsubsetassign or viewexists statement, with the error saying it cannot find the view even though it is stated in the Data Source, and the preview returns. I've run the same processes on other .Vue views and it works just fine. 

    I'm wondering if anyone has experienced this or can tell me why it is happening (or supply a fix ? ) as with the Remote Desktop now deprecated. We have no way to run these critical processes. 



    ------------------------------
    Phillip Lidstone
    ------------------------------


  • 2.  RE: xbf views and TurboIntegrator Issues

    Posted 23 hours ago

    Hi Phillip,

    Yes, the TM1 native views had been saved as the MDX views, the warning that the views will be replaced were given upon saving.

    The isssues with the process data sources would be expected as the MDX view would impose a different order and not match the process data source ste up. 

    If you have the TI processes to recreate those views, then you should be able to continue to use them as a datasource.

    The option to save the view as the native view or MDX view is going to be available on the next PAW release in October 2024.

    Best regards,



    ------------------------------
    Svetlana Pestsova
    IBM Planning Analytics Product Manager
    ------------------------------



  • 3.  RE: xbf views and TurboIntegrator Issues

    Posted 2 hours ago

    Svetlana, the issue I have is that the TI process doesn't even recognise that the view exists. Even when I run Bedrock the ViewExists statements fail. 

    I can delete the view and use Bedrock to set them up again each time, but to make small adjustments each time this is very long winded. 



    ------------------------------
    Phillip Lidstone
    ------------------------------



  • 4.  RE: xbf views and TurboIntegrator Issues

    IBM Champion
    Posted 20 minutes ago
    Edited by Wim Gielis 18 minutes ago

    Phillip,

    I do wonder why you would need those views in the first place in your database, with a name that users can attribute meaning to ? Even more, can your users save/overwrite the views ? I see that you write about inexperienced administrator users. Then I can understand overwriting but there's definitely a need for training then.

    What I do is have 1 ZZZ_Tmp public view on each data cube. It can be easily created with a TI process.

    The view is not huge, rather, it's the most tiny view you can imagine: 1 cell. Meaning, 1 element per dimension, all dimensions stored in the Context area,

    and the order follows the order of the cube dimensions.

    Yes, technically, users can still open and overwrite, but chances are rather small.

    Each dimension (that appears in any of these cubes) will have a ZZZ_Tmp public subset too, containing 1 element. The first element in the dimension.

    The Prolog tab then creates and assigns a new (temporary) view to the process and the rest is as expected.



    ------------------------------
    Wim Gielis
    ------------------------------