Skip to main content

Users are reporting issues with Nintex forms rules all of a sudden.
I have a simple form with a checkbox with a validation rule.
The checkbox is connected to a SharePoint list field “DeductFromSalary” of the type YES/NO.
 

 

The behavior with this rule is just weird​.

 

When I check the box… the validation message appears. That should NOT happen as the validation rule is set to display the message when the box is NOT checked.
 

And once it’s displayed… it won’t go away anymore.
I can check/uncheck as much as I want… the message stays there.

When I remove the “not()” function from the condition, everything seems to be fine. The validation message is displayed when the checkbox is checked and disappears when the checkbox in unchecked. It seems like an issue with the NOT function that is used.

We didn’t change anything on the environment. It’s a SharePoint 2019. No updates, no configuration changes, nothing. It has been working up until yesterday… and today it fails. I tried replicating this on a different site collection and I have the exact same issue.
Also other users on different sites and forms are reporting similar issues with forms that stopped working. All of the issues are related to rules that for some reason are not doing what they should be doing. Every rule where built-in functions are used, seem to be broken.
A rule where a date/time manipulation is done worked 2 years without any issue… suddenly it returns a “#Value!” instead of a number.
Makes no sense.
 

Hi @bkuppens,

In an on-premise environment, Nintex cannot change anything remotely.
This means something has changed in your environment. When I say environment, I am not just referring to SharePoint but also to the Standard Operating Environment installed on company machines.
Has there been an update to the browser being used? Has more security been added?
Is this being blocked, as Nintex forms rely on Javascript?  Looking at the browser development tools may give you a clue as to the issue.
 

Thanks for the response @SimonMuntz .

I wanted to check the dev console for other clues but it seems that the issue resolved itself.
All rules are behaving normally and the behavior we had yesterday, is gone.

Very strange since I checked with the infra guys that manage these servers and they ensured me that nothing had changed.

But I agree that something that works for 2 years doesn’t break overnight if nothing changed.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings