when multiple values is selected for date/time component, default value moment() is not honored

[Bnayak123]

{ "display": "form", "components": [ { "label": "Date / Time", "tableView": false, "datePicker": { "disableWeekends": false, "disableWeekdays": false }, "multiple": true, "defaultDate": "moment()", "enableMinDateInput": false, "enableMaxDateInput": false, "key": "dateTime", "type": "datetime", "input": true, "widget": { "type": "calendar", "displayInTimezone": "viewer", "locale": "en", "useLocaleSettings": false, "allowInput": true, "mode": "single", "enableTime": true, "noCalendar": false, "format": "yyyy-MM-dd hh:mm a", "hourIncrement": 1, "minuteIncrement": 1, "time_24hr": false, "minDate": null, "disableWeekends": false, "disableWeekdays": false, "maxDate": null } }, { "type": "button", "label": "Submit", "key": "submit", "disableOnInvalid": true, "input": true, "tableView": false } ] }

[travist]

Interesting... it seems that because you selected multiple, and the default is a moment value that it forces it to not be an array and it creates a validation error. I do see this as a bug, but it would be considered pretty low priority.

[olgabann]

Thank you for reporting this issue. I can reproduce it and have logged a ticket for the backlog. We are always willing to review any contributions to resolve this issue from the open-source community.

For internal reference: FIO-8204

[lane-formio]

There is a workaround for this behavior by utilizing the data grid and adding the date/time component instead of using the multiple values option in the date/time component itself. I would suggest trying that. If someone would like to contribute a solution to fix the multiple values / default moment() value we'd be happy to take a look!

I'll leave the issue open for the time being.