Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only
Back to discussions
Expand all | Collapse all

PAfE #NUM! Errors

  • 1.  PAfE #NUM! Errors

    Posted 02/26/24 09:13 AM

    One specific PAfE user gets #NUM! errors. They don't come always and they don't occur consistently in the same range of formulas. 
    We cannot reproduce the issue on other workstations.

    Has anyone seen this before or maybe have a clue where to look to fix this?

    We're using "IBM_PAfE_x86_2.0.89.3.xll", but we have also tried with a more recent version "IBM_PAfE_x86_2.0.93.6.xll".

    Thanks in advance.



    ------------------------------
    Herman Teeuwen
    ------------------------------


  • 2.  RE: PAfE #NUM! Errors

    Posted 02/26/24 09:17 AM

    Hi Herman,

    #NUM! could also be down to security where the user does not have permissions to the cube, elements etc.



    ------------------------------
    George Tonkin
    Business Partner
    MCI Consultants
    Johannesburg
    ------------------------------



  • 3.  RE: PAfE #NUM! Errors

    Posted 02/26/24 09:27 AM
    Edited by Herman Teeuwen 02/26/24 09:27 AM

    Hi George,

    I don't think that in this case this could be due to security because the #NUM! errors don't appear in the same formulas. 
    In one case, they show values, and in the next case, they show #NUM! errors.

    Best,



    ------------------------------
    Herman Teeuwen
    ------------------------------

    Original Message


  • 4.  RE: PAfE #NUM! Errors

    Posted 02/26/24 09:35 AM

    Have you tried the magic PAfE Keys?

    Ctrl + Shift + F9 or Ctrl + Shift + Alt + F9 - this seems to clear cache etc. and was mentioned by Ted on an AMA



    ------------------------------
    George Tonkin
    Business Partner
    MCI Consultants
    Johannesburg
    ------------------------------

    Original Message


  • 5.  RE: PAfE #NUM! Errors

    Posted 02/26/24 09:51 AM

    Thanks for the pointer George!

    I just asked the user to test this, but it does not resolve the issue, user sees even more #NUM! errors than before (and some formulas just showing values).



    ------------------------------
    Herman Teeuwen
    ------------------------------

    Original Message


  • 6.  RE: PAfE #NUM! Errors

    Posted 02/27/24 01:42 AM
    Have you checked the workbook for standard excel issues and/or PAfE logging?

    Circular References
    Broken Links
    Large amounts of invalid named ranges
    Large amounts of hidden named ranges
    Tried removing the @ sign in front of the formula
    Checked your office build number vs other users
    Cleared the PAfE cache
    Turned on logging and looked at the .har file in fiddler





    Robby
    Details about the personal data CBRE collects and why, as well as your data privacy rights under applicable law, are available at CBRE – Privacy Policy.<https: www.cbre.com/about/privacy-policy/policy-picker="">


    Original Message


  • 7.  RE: PAfE #NUM! Errors

    Posted 02/27/24 01:26 PM

    Hi Herman,

    I have seen this issue with users and was able to reproduce with admins too. I am assuming security is correct and this is Custom report. Updating the below parameter as true in tm1features.json file in local profile of user helped fixing this problem. Try this and let me know how you go.

    thanks

    Mohit

    {"r68_DisableNewCRValidator": true}


    ------------------------------
    Mohit Gupta
    ------------------------------



  • 8.  RE: PAfE #NUM! Errors

    Posted 02/27/24 01:53 PM

    Dear Mohit,

    Yes, security is correct and this is about a custom report.

    Thanks for the pointer. I sent tm1features.json with this entry plus instructions to the user/

    Will report back.

    Best regards,



    ------------------------------
    Herman Teeuwen
    ------------------------------

    Original Message


  • 9.  RE: PAfE #NUM! Errors

    Posted 02/28/24 02:23 AM

    Unfortunately this tm1features.json entry did not resolve the issue, still #NUM! errors in reports.

    We're now trying to determine whether the issue is really workstation-related by having the user try from a colleague's workstation (who has confirmed that the report works normally and does not show any #NUM! errors).

    Best regards,



    ------------------------------
    Herman Teeuwen
    ------------------------------

    Original Message


  • 10.  RE: PAfE #NUM! Errors

    Posted 02/28/24 04:45 AM

    HI Herman, seems like I gave you the incorrect sequence of keys above - the first one should have been Alt+Shift+F9

    Could you see if that helps the user if the workstation switch or "problematic" user on a working PC does not work out for you?



    ------------------------------
    George Tonkin
    Business Partner
    MCI Consultants
    Johannesburg
    ------------------------------

    Original Message


  • 11.  RE: PAfE #NUM! Errors

    Posted 02/28/24 04:52 AM

    Hi George,

    Will do that, thanks.



    ------------------------------
    Herman Teeuwen
    ------------------------------

    Original Message


  • 12.  RE: PAfE #NUM! Errors

    Posted 03/01/24 08:02 AM

    Issue is definitely related to workstation of user.

    User logged in with her own credentials on workstation of a colleague that does not get these #NUM! errors, and there she also does NOT see #NUM! errors.

    The other way around, if this colleague logs in with own credentials on workstation of user who's reporting the issue, this colleague also gets #NUM! errors. 

    Then I thinks I will go for a re-installation of Office 365 on user's workstation, and see if this resolves the issue.



    ------------------------------
    Herman Teeuwen
    ------------------------------

    Original Message


  • 13.  RE: PAfE #NUM! Errors

    Posted 02/28/24 11:27 AM

    Hi,

    We have users who are also seeing these #NUM! errors. The first thing that was noticed was that explorations could not be converted to custom reports in PAX but they could be converted to Quick and Dynamic reports.

    I determined part of the issue was due to a new dimension being created for the cube in question and no dimension security was applied.

    However, while this resolved the converting explorations to custom reports the #NUM! errors have persisted. I have a theory that because the new dimension shares the exact same names as elements in another dimension this is causing some ambiguity issues. Does that like a sound reasonable theory?

    I can see nothing else that would explain this, though it should be pointed out that Admins do not see these errors, which does undermine the theory!

    regards,

    Mark



    ------------------------------
    Mark Wragg
    ------------------------------



  • 14.  RE: PAfE #NUM! Errors

    Posted 07/07/25 01:31 PM

    Hi @Herman Teeuwen,

    Were you able to find root casue of this issue and fix for it?

    We are currently also facing same behaviour on custom report for only one of our user.

    Cheers,

    Vivek



    ------------------------------
    vivek kumar
    ------------------------------



  • 15.  RE: PAfE #NUM! Errors

    Posted 07/08/25 01:31 AM

    Hi Vivek,

    No, we never identified the root cause of the issue.
    It was clearly workstation-related, as the problem disappeared after the user's notebook was replaced.

    Best regards,
    Herman



    ------------------------------
    Herman Teeuwen
    Canon Production Printing
    ------------------------------

    Original Message


  • 16.  RE: PAfE #NUM! Errors

    Posted 07/08/25 02:54 AM

    Hi Herman,

    Thank you for reply.

    CHeers,

    Vivek



    ------------------------------
    vivek kumar
    ------------------------------

    Original Message


Related Content