ok, I've figured out that it's the dateDiffDays function that is causing this error and have recreated the issue with other classic forms. 

Has anyone else experienced an issue with this function in forms when upgrading from 2013 to 2016? If so, what is the solution? 

Thanks again,

Kassie

We encountered a similar error after upgrading to Nintex Forms version 5.2.2.70 last night.

Some of our forms are using the formula dateDiffDays and the {Common:CurrentDate} system property. e.g. dateDiffDays(Commencementdate, {Common:CurrentDate}). It was working yesterday prior to the patch.

I found changing {Common:CurrentDate} to another form property resolved the issue.

My workaround was to create a calculated property and set it to {Common:CurrentDate}. I then reference THAT calculated field in my dateDiffDays formula.

I have submitted a helpdesk ticket with Nintex to ask whether the previously available functionality can be restored. The initial response was, 'we see you have found a solution, can we close the ticket now?'.

I agree, the workaround is not a long-term solution. We have built so many forms, it would be difficult to find and change every one using this function in one of the formulas. 

It's a built in function, it needs to work. Our admin opened a ticket with Nintex as well. Maybe it will get more attention now that there's more than one...

Excellent. I've now been informed support have been able to replicate the issue and have referred it to the development team.

yea, it's taking a while for a fix. 😕

The workaround posted above does work though. I'm not sure if you're formula calc allows it. 

Here's a screenshot of mine.

The new calculated field to get the current date:

Then I replaced all the current date references in my formula with "TodaysDate" calculated field value. It's working now. 

If(not(equals(RequestType,"Job Jar")),If(equals(formatDate(TodaysDate,"dddd"),"Monday"),dateDiffDays(TodaysDate,RequestedSwitchingTime),dateDiffDays(TodaysDate,RequestedSwitchingTime)-2),If(or(equals(formatDate(TodaysDate,"dddd"),"Thursday"),equals(formatDate(TodaysDate,"dddd"),"Friday")),dateDiffDays(TodaysDate,RequestedSwitchingTime)-2,dateDiffDays(TodaysDate,RequestedSwitchingTime)))

Just found a workflow with a build string action using the "fn-DateDiffDays" while testing our 2016 environment pre-upgrade. This function isn't working in workflows either, and the workaround doesn't work if I try to set a variable to capture the current date, then use that in the formula. 

Any thoughts on a workaround for the function not working in workflows?

Thanks!

We might need someone else with SharePoint 2016 to test.

The formula seems to be working in Nintex Forms and Nintex Workflows in SharePoint 2019.

Nintex Forms version 5.2.2.70.

A workaround would be the following but the DateDiffDays would be preferable by far:

(Date2 - Date1) / (1000 * 60 * 60 * 24)

or

(Date2 - Date1) / 86400000

*Assuming 'Date2' is always the later date. Otherwise we have to add if statements to change the order.

If you can email or post an example of your calculation step I could test that and see if I can replicate.

I've attached the successful fn-DateDiffDays formula usage in our environment.

Hi All,

I just ran into this as well, Found a very simple solution. Just add a runtime function isDate() before your date named control.

Worked for my error.

Regards