Hi Jason,

The form is set up so anyone can access it using it (public anonymous access). So my personal regional settings should not be an issue. But I've checked both mine and the account the data connection is using to connect to SharePoint online: Both have the correct regional settings (UTC+8:00). The Same for the Site collection the list is on and in the NWC Form settings.

The tenant regional settings should not affect at all correct? as it's been overridden by the Site COllection Regional settings?

@Rizi Date fields are always passed as a UTC date/time and SharePoint date only fields still have time component that is just hidden on the view. You can use a log to instance detail to see the time being passed. The screenshot below shows the UTC time as well it being converted both US and an Aus timezone using the convert date to string action.

It could be the users personal regional settings causing the issue(https://support.microsoft.com/en-us/office/change-your-personal-language-and-region-settings-caa1fccc-bcdb-42f3-9e5b-45957647ffd7). The other option is converting the date to a timezone and putting in a text field or using the add time to date if you can't resolve the regional setting.

Hi @Rizi ,

I was able to get this to work in my test environment by doing the following:

1. First I checked the Create an item action to see if it would accept a text variable to set a date column in the list and it does. 😀



2. Next, I manually inserted a date in the Create an item action to see what date format is required:
   



3. Now that I knew what format is required, I added a Format date to string action to my workflow above the Create an item action and stored the formatted date in a text variable named txtDOB. This also allows me to specify a time zone. 
   



4. Because the exact format option I needed wasn't available, I also added a Create a text string action to finalize the formatting:
   



5. Finally, in my Create an item action, I inserted the txtDOB variable into the DOB date column field:
   



6. The completed workflow looks like this:
   
   
   

   This corrected the date in my SharePoint Online list. Give it a try and see if it works for you.

   
   
   

I was also able to reproduce the issue.

One thing that worked for me was to change the date format of the Date and Time column in SharePoint to  Date & Time under the Additional Column Settings section.

I also configured the date control on the NWC form to turn off the Hide Time setting.

I think this way the date time format comes in from the NWC form with the full date and time based on when the date was selected then SharePoint can store it with the correct UTC value. Ultimately, you may need to ensure that you have the time designated with the date as it gets stored in SharePoint.

This was a Bug in NWC. Opened a Support Case with Nintex Support and they have applied a fix for it. All working as expected now.

Thank you for all your help