Calculate Date Action in Nintext for SharePoint 2016 - Calculation issue


Badge +5

I have a customer that wants to calculate specific dates ever year for reviewing items in a list (uses flex task too).  

So an item that's been reviewed on 1/31/19 should roll to the next review on 4/30/19.  The 4/30/19 should roll to 7/31/19.  And 7/31/19 should roll to 10/31/19.  Then, starting over, the 10/31/19 should roll to 1/31/20.  You get the idea.

I calculated in Excel the datedif between these dates.  See image below:

3002i179DE48213F6FD44.jpg

There should be 92 days between 10/31 and 1/31.  This shouldn't change from year to year (unless I live on another planet).

However when I put the Calculate Date in as below (10/31/2019) is sitting in the Next Review Date field it only adds 89 to the Next Review Date and calculates 1/28/2020.  That's three days less than what I put into the formula below.

3003iCF38DDCF9E42AF71.jpg

I've tried all sorts of stuff to make the date come out correctly.   I've put in 95 days but it still calculates wrong.  I've tried 3 months.  Still calculates wrong.

Does anyone have any ideas why this might be calculating wrong?

 

 


4 replies

Badge
Hi, It seems to me that the add to date action is only letting you add 90 days. I would suggest finding a large number you can put in and get consistent results (lets say 80) and then add the rest in a second action afterwards. e.g. 10/31/2019 + 80days = 1/19/2020 + 12days = 1/31/2020.
Badge +5

I think it's a Nintex bug.

Userlevel 5
Badge +14

could you try following?

- write value of NextReviewDate to history log

- set up a loop from 0 too 100

    - within the loop calculate date, add up value of loop index days to NextReviewDate 

    - write calculated date value, along with index value to history log

 

could you identify when the deviation starts/happens?

 

 

 

do you have any difference in server's, site's, your SP user profile's regional/timezone settings?

how/where exactly did you check source and calculated dates?

 

 

 

 

Badge +5

Thanks for responding.  No change in environments on premise.  Our workflows run on east coast time.  But that's it.  I may try this.  I think Nintex should figure it out and fix it.

Reply