Hi all,
Just been trying to use a Date&Time Widget in a Data App for a user to select Start and End date for data visualization.
In order to prevent errors I extracted min/max date from the input data to then define min/max flow variables in the widget. I also wanted to use the min date as the default value for the “Start Date” Input and the max date as the default value for the “End Date” Input.
This turned out to be very tricky - whereas the min/max flow variable inputs don’t seem to have issues with “yyyy-MM-dd” string input, the default kept throwing an error that the date cannot be parsed.
I went back to 2020 in the forum to find a resolution:
The current workaround is to edit the string to comply Date&Time with Timezone format so that the variable value passed in as default looks like this:
2028-08-01T01:00:00+02:00[Europe/Berlin]
It appears that the default value always expects date&time incl. timezone information - even though the Type as been set to “Date” and not “Date&Time”:
Suggestion: Make the validation for default value provided via flow variable more lenient - i.e. distinguish between Type = “Date&Time” and Type =“Date” and parse the variable accordingly. It seems inconsistent to how min/max are being handled…