Date picker in request form returns wrong date

Stephane_Bouillon

Hi, I have a request offering form where I use a date field. When the end user selects a date, for example April 30th 2018, it is displayed as 4/30/2018 12:00 AM. When I map this to for example the title, this date string is copied.

However, when I check the UserInput field, it is modified and stored as 2018-04-29 22:00:00 UTC". I need to add an SMA script in which I want to do something based on the date and there I'm also stuck with the wrong converted date.

Any ideas how I can get around this ? Obviously I want to work with the date that the end user selected.

Stephane

Adam_Dzyacky

System Center (and I truly do mean all of the products) store datetime in UTC format. When it comes to working with SCSM, PowerShell, SCO/SMA your best bet is to do a conversion from that UTC time to your respective local time zone. Take the following PowerShell example:

[datetime]$startDate = $utcStartDate
[datetime]$endDate = $utcEndDate

[datetime]$startDateTime = [System.TimeZone]::CurrentTimeZone.ToLocalTime($startDate)
[datetime]$endDateTime = [System.TimeZone]::CurrentTimeZone.ToLocalTime($endDate)

$startDateTime.ToString()
$endDateTime.ToString()

In doing so you can let System Center keep on being System Center and still get what you need.

Adam_Dzyacky

System Center (and I truly do mean all of the products) store datetime in UTC format. When it comes to working with SCSM, PowerShell, SCO/SMA your best bet is to do a conversion from that UTC time to your respective local time zone. Take the following PowerShell example:

[datetime]$startDate = $utcStartDate
[datetime]$endDate = $utcEndDate

[datetime]$startDateTime = [System.TimeZone]::CurrentTimeZone.ToLocalTime($startDate)
[datetime]$endDateTime = [System.TimeZone]::CurrentTimeZone.ToLocalTime($endDate)

$startDateTime.ToString()
$endDateTime.ToString()

In doing so you can let System Center keep on being System Center and still get what you need.

Stephane_Bouillon

Thanks Adam,
 The UserInput field contains the correct data, but when it is run through the Get-SCSMWorkItemUserInput cmdlet the date is no longer correct. So I'll have to re-parse it from the original UserInput field on the SR.

Stephane

Stephane_Bouillon

I finally decided to parse the UserInput xml myself rather than relying on the Get-SCSMWorkItemUserInput cmdlet, this way I could handle the date field(s) correctly from the start. Thanks for your help Adam.

Marek_Lefek

So to have a proper time in eg. Title field I need to create runbook ? Aren't there any easier way?