Skip to Main Content
Nintex Ideas

đź‘‹ 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 are looking for the Nintex roadmap, you can find that on Nintex Community

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

Status Completed
Categories Runtime
Created by Guest
Created on Jul 3, 2017

String to date action

We need to have a more complete approach to manipulating dates.

Scenario: External start receives a date value to a date field. Another systems (CRM Query Record action for example) take the date in another format.

Issue: Can't pass the variable to the Salesforce Query Record action as you can't get the date in the right format

Potential short term fix: Create a string to date action - we pass the date to the external start variable (string), maipulate string into right format, use 'string to date' action to set a date variable in a format that the Salesforce query record action understands

Long term fix: Inline functions on string actions perhaps
  • ADMIN RESPONSE
    Sep 7, 2022
    This is currently planned where the Convert a value action will be extended to support string to date.
  • Attach files
  • Dan Stoll
    Reply
    |
    Sep 7, 2022
    Unable to modify Date variable formats and save back to date variable. or convert string to date.
  • Guest
    Reply
    |
    Sep 7, 2022
    OOB String to date conversion is still needed and makes working with dates pretty painful whenever you need to interact with anything external.
    When adding, please also allow for specifying the format to be parsed, otherwise we will all end up with requests to add more date formats (just like with the date to string requests).
  • Brady
    Reply
    |
    Sep 7, 2022
    Just curious on the upcoming implementation of this as part of the "Convert a value" action.

    Will this conversion involve specifying what time format and zone the string represents? If so, can it account for Daylight Savings Time? Currently, when referencing datetimes in a workflow, those will fluctuate by an hour if you observe DST. This requires manually editing and republishing the workflow to adjust for that hour. If this feature could provide a way around that, that would be great.