mpinuel
Forms Fledgling

Calculated fields don't show the value in SharePoint Online

Jump to solution

For a few days we are experiencing intermittent errors in our Nintex Forms in SharePoint Online. Without having made any changes or published new versions, sometimes the Calculated Fields of the forms don't show their value and instead their show: #Value!image.png

 

image.png

 

It seems to be something intermittently, and it happens with different users (included admin accounts), different environments (sites), and we've reproduced it in all the browsers (IE, Edge, Chrome and Safari) but it always happens with the Calculated fields of the Nintex Forms.

 

Also we've detected that, when the calculated fields are not shown (with the #Value! error) all fields and panels that have a Formatting rule are not seeing in the Form.

 

Please, has anyone else had an error similar to this?

Thanks!

0 Kudos
Reply
2 Replies
SimonMuntz
Nintex Employee
Nintex Employee

Re: Calculated fields don't show the value in SharePoint Online

Jump to solution
Hi,
When the issue occurs look in the Browser console for clues as to what may be happening. Rules and calculated values end up being Javascript and it looks like the javascript is being blocked by something.
0 Kudos
Reply
mpinuel
Forms Fledgling

Re: Calculated fields don't show the value in SharePoint Online

Jump to solution

Hi,

Finally Nintex Support team was able to solve the problem. They have given us this information about the error, which I share in case something similar could happen to someone in the future:

 

Nintex Forms O365 use Azure Cloud Service with several instances running to share load for each region. When they do deployment, it restarts all the instances, but during the last deployment one particular instance didn't start properly so eventually it wasn't working properly. So whenever user loads the Nintex Form, and if it goes to that instance, it will not process calculated value functions properly and it will give #value!.
They have restarted that particular instance only and it looks like issue has been resolved.

 

Thanks for the reply!

Regards,

View solution in original post

0 Kudos
Reply