JSON Deserialize Step Date field issue
Comments
-
Hi,
I have an issue with the regional date format. I’m using to deserialize a string being returned from an external rest service (Deserialize step).
When the day of date value is less than 13 (Europe format) it works. It’s obviously a regional formatting issue but I don’t know how to resolve it for this step to work.
Thanks
-
Hi,
Unfortunately, we do not have a native setting for data structure Date type conversion for the moment. However, you can use a workaround to fix this issue. For the workaround, you should change the data type of Date property in the JSON structure to String and use Parse Date with Format step after JSON Deserialize step. So, JSON Deserialize step will output date values as a string and you will format this value by using Parse Date with Format step. Please check below forum post for details. If you have to use this conversion in many places, then you can create a converter flow and apply it in necessary flows. Please check the below link about building converter flows.
https://support.decisions.com/forum/topic2550-date-format-issue.aspx
https://documentation.decisions.com/docs/using-converter-flowsRegards
Howdy, Stranger!
Categories
- 4.1K All Categories
- 61 General
- 11 Training
- 201 Installation / Setup
- 1.1K Flows
- 106 Rules
- 260 Administration
- 212 Portal
- 489 General Q & A
- 693 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 51 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 178 Pages
- 5 Process Mining
- New Features
- 178 Datastructures
- 69 Repository
- 219 Integrations
- 28 Multi-Tenant
- 27 SDK
- 76 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 66 Lunch And Learn Questions