Planning Analytics

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.

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

Original Message:
Sent: Mon February 26, 2024 09:12 AM
From: Herman Teeuwen
Subject: PAfE #NUM! Errors

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
------------------------------

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:
Sent: Mon February 26, 2024 09:17 AM
From: George Tonkin
Subject: PAfE #NUM! Errors

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

Original Message:
Sent: Mon February 26, 2024 09:12 AM
From: Herman Teeuwen
Subject: PAfE #NUM! Errors

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
------------------------------

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

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:
Sent: Mon February 26, 2024 09:17 AM
From: George Tonkin
Subject: PAfE #NUM! Errors

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

Original Message:
Sent: Mon February 26, 2024 09:12 AM
From: Herman Teeuwen
Subject: PAfE #NUM! Errors

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
------------------------------

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).

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

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:
Sent: Mon February 26, 2024 09:17 AM
From: George Tonkin
Subject: PAfE #NUM! Errors

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

Original Message:
Sent: Mon February 26, 2024 09:12 AM
From: Herman Teeuwen
Subject: PAfE #NUM! Errors

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
------------------------------

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.

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}

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.

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,

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}

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.

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,

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,

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}

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.

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?

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,

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,

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}

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.

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,

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,

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}

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.

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.