đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
I have a Scheduled start workflow that runs daily to search a SharePoint list, looking for a date six weeks (42 days) in the future, then returning any "hits" it finds among the list items. At least that's what it is supposed to do. The problem is that there is an incompatibility between the date as formatted in Nintex and the date in SharePoint.
If I use the Add time to date function in Nintex to calculate the future date, it returns a value in ISO 8601 format (date and/or text format, whichever I choose). The date in SharePoint is in M/D/YYYY format. Therefore, when Nintex looks for the date, it will not find it in the SharePoint list. I confirmed this on a date when I knew for certain that one "hit" should have been returned, but none were.
I was able to develop a workaround by converting the dates in Nintex and SharePoint to strings and then comparing, but this seems like something that shouldn't have to happen. Nintex should be able to look for and find dates in SharePoint just as it can for text, numbers, etc. Is there a way to make this happen?
On a similar note, I would also like to request the addition of M/D/YYYY format to the Format date to string function. You can convert a date to this format within a form, but not in the workflow. The closest format is MM/DD/YYYY. For emails, task forms, etc., a day like today (March 5, 2025) looks better as 3/5/2025 than as 03/05/2025.
