For example, I use a ParseExact(“2026-04-06T00:00:00”,“yyyy-MM-ddThh:mm:ss”,System.Globaliszation.CultureInfo.Invariant) statement to get the amended value into data structure.
The value is passed to Action Center with a Create Task.
The issue is that Action Center sees the value but says that it is NOT in the correct format “yyyy-MM-dd”. It shows the value as dd/MM/yyyy - which reflects my UK local format.
For date fields that are not changed since the extraction, Action Center is OK.
Is there an approach in UiPath Studio to assign a value into a Date field so that it is “Stored” in the format Action Center expects?
Then assign it directly to the Date field (no .ToString()).
The dd/MM/yyyy you see is just UI localization (UK format). Internally the value is still valid. If Action Center rejects it, check that the field isn’t being converted to String anywhere in your workflow.
Are you using an Action Center Custom Form that you created? Or are you using the standard Document Validation Station?
I often use Custom Forms in Action Center and have successfully passed Date values. But before I show some screenshots, let me know how you are presenting the fields.
So usually Action Center expects the input passed as Strings.
Have you tried converting it to a String using InvariantCulture and then passing it into Action Center in the correct format? Converting it to a String gives you the ability to force the expected format.
I had tried that option, but as the structure is created by IXP extraction, UiPath in Studio insists that it is a date field and will only accept a date value being assigned to it.
If its the issue I think it is, there is not really a workaround, cause its the server messing up and then returning the data in a format that then breaks the activity in Studio from reading it, so you don’t get a chance to correct the output.
It can technically be worked around, but you need to go super hard deep into the Document DOM file that gets added to the storage bucket when the action is created and completed, and get that changed. Its not something easy enough for anyone to do, I think it took me a long long time to figure it all out to really prove the bug to them as they kept telling me it was regional settings on my machine, which it 100% was not.