Planning Analytics

 View Only
Expand all | Collapse all

PAW 2.0.90 > 2.0.93 upgrade with distributed setup. UR & TM1Set no longer work

  • 1.  PAW 2.0.90 > 2.0.93 upgrade with distributed setup. UR & TM1Set no longer work

    Posted Tue March 12, 2024 10:58 PM

    It's not truly a distributed setup but found it was necessary in order to get TM1Set and UR working in .90.

    I have the same settings in the config files in .93 as I had in .90 as per the following instructions.

    https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=reports-configure-evaluationservice-distributed-tm1-deployments

    Anyone else have a distributed setup and it works in .93?



    ------------------------------
    John O'Leary
    ------------------------------


  • 2.  RE: PAW 2.0.90 > 2.0.93 upgrade with distributed setup. UR & TM1Set no longer work

    Posted Wed March 13, 2024 06:10 PM

    Need to understand some of the details on the upgrade, would not generally expect a compatibility break in that span (if mixing versions) for any previously working arrangement, unless it was otherwise mentioned in the release notes as an exception. 

    Best course of action is to get a case going, if you can. (send me the number if you have one)

    If you do have a need to use those settings, may also be able to suggest a refinement of the values based on your deployment scenario. It remains the case that the expectation is spreadsheet features should work out of the box (with no manual configuration) unless there is a 'distributed' TM1 services install or other unusual network topology.



    ------------------------------
    Ted Phillips
    IBM
    ------------------------------



  • 3.  RE: PAW 2.0.90 > 2.0.93 upgrade with distributed setup. UR & TM1Set no longer work

    Posted Tue April 16, 2024 10:19 PM

    Cycling back on this. I reinstalled PASS (In Dev only - as it ended up being ok in Prob) and the issue was resolved. We still need to use the Evaluation Service and but unfortunately we have found that Universal Reports don't work with Aliases containing the "&" character and we have "Code & Description" as an alias in most dimensions. This is not in line with recommended naming conventions but I know we would not be the only site with that naming convention.  PAfE .90 did not display errors, it just didn't work (So in hindsight I now know what UR didn't work for me in many cases) but in .93 it throws an error though not a very useful one. Works fine with Member ID. 



    ------------------------------
    John O'Leary
    ------------------------------