Hi @Andy E​ ,

I was unable to reproduce the behaviour that you're experiencing. What DateTime value are you manually inputting? Are you able to share a screen recording and/or sample workspace for me to take a look at? If you restart FME Server, does any thing change?

Thanks,

Kezia

Its happened again, this time restarting the servers hasn't resolved it.

Two issues:

1. When the date time picker appears, changing the date only changes the month and day, not the year;
2. When the picker doesn't appear, clicking on the button doesn't work, just raises messages in the console;
3. typing in a date results in "Invalid Date" being passed when clicking run.

Video attached

Hello @Andy E​ ,

Would you be able to provide the workspace with sample data tyou can save the workspace as a template], since we are unable to reproduce this issue?

Hi @Merline George​ ,

Apologies took some time to get a sample workspace together, attached here. This workspace has 2 date time parameters with default dates in the past.

Using the run workspace page on FME Server the first time will present the correct dates in the fields, although the date time picker is set to 2017 regardless of the default dates. Actually running the workspace will result in "Invalid date" being passed as the actual date parameter.

Trying to run the same workspace again through the web UI results in no values in the fields and the date picker will not work at all.

Workspace created and published with MacOS FME 2022.1.2 (build 22627), and works correctly when launched through the REST API, so I'm pretty sure its a web app issue (FME Server is running on windows, same build as desktop, 22627)

Thanks