Datetime parameter unusable in simple automation runbook

Buch, Tamara 11

I have the most simple runbook imaginable. It takes the parameter [Datetime]$DateNotified and it does a write-output of $DateNotified. Instead of printing the date I get this error: Cannot process argument transformation on parameter 'DateNotified'. Cannot convert value "/Date(1678838400000)/" to type "System.DateTime". Error: "String '/Date(1678838400000)/' was not recognized as a valid DateTime."

Any ideas why? I just want users to be able to select a date when running a runbook, but anything I do with a [datetime] param throws an error. See screenshots.

azure2

azure1

User's image

Buch, Tamara 11 Reputation points

2023-03-30T18:36:42.0033333+00:00

This is definitely to do with the time picker. If I set a default date in the parameter block and use that, it will work. It only fails when using the time picker to select the parameter.
tbgangav-MSFT 10,386 Reputation points

2023-04-06T03:09:39.3033333+00:00

@Buch, Tamara , Apologies for any inconvenience caused and thanks for bringing up the issue and also sharing the workaround. I am checking internally with the product team regarding the issue. We shall hopefully update you with some investigation findings and insights in couple of days.
Michal Jarzab 31 Reputation points

2023-04-18T14:09:53.6566667+00:00

I have the same issue :/
tbgangav-MSFT 10,386 Reputation points

2023-04-19T17:25:38.85+00:00

Hi @Buch, Tamara and Michal Jarzab, Internal product team has identified the fix and are working on it. Will keep you updated with ETA or with updates as I hear more information.
Gordon Wong 0 Reputation points

2023-04-24T15:54:56.3333333+00:00

I am having the same issue as well. Any updates on when this will be fixed?
tbgangav-MSFT 10,386 Reputation points

2023-04-24T17:14:08.55+00:00

Hi @Buch, Tamara, Michal Jarzab, and Gordon Wong, The fix is in validation and is expected to be deployed in next service deployment. It would be rolled out to all regions by 5/15. Will keep you updated as I hear more information.
Gordon Wong 0 Reputation points

2023-05-18T17:52:22.7366667+00:00

Has this been fixed? I am still getting the same issue.
Buch, Tamara 11 Reputation points

2023-05-18T18:03:19.3466667+00:00

@Gordon Wong It is still not working for me either. This only appears to be an issue with Powershell 7.1 runbooks. It works fine in Powershell 5.1 and Powershell 7.2.

I have a case open with Microsoft and they seem to suggest the team knows about it but who knows when they'll fix it, so don't wait up.
Gordon Wong 0 Reputation points

2023-05-18T18:09:46.5566667+00:00

Thanks. Mine is running on PowerShell 5.1 and it's not working.
tbgangav-MSFT 10,386 Reputation points

2023-05-19T06:56:09.7733333+00:00

Hi @Buch, Tamara, Michal Jarzab, and Gordon Wong,

Yes, it's fixed for 7.2 runtime! PowerShell 7.1 is out of support by PowerShell team and we are not investing in enhancement of this version support in Azure Automation. Is it possible for you to start using 7.2 instead?
Gordon Wong 0 Reputation points

2024-01-30T16:08:50.5366667+00:00

Looks like it stops working on 7.2 now and still not working on 5.1. Everything works locally.
Asta Hansen 0 Reputation points

2024-02-21T10:08:47.32+00:00

This no longer works for me as well on 7.2 runbooks

Cannot process argument transformation on parameter 'RunDate'. Cannot convert value "/Date(1708473600000)/" to type "System.DateTime".