Date/Time field in Multi-Row Variable Set not capturing correct time

[marianneurnes]

Hi all,

I'm having some trouble with using the date/time field in multi-row variable sets. I've created a dummy catalog item to illustrate the problem. I need to capture multiple instances of work start and work end values, which should go well with the functionality of a multi-row variable set. However, when trying to order the catalog item with this variable set, the date/time registered is shifted with one hour after checking out the item:

This is a screen shot from the sp-portal, where I can access the catalog item. "Reg start" and "Reg end" are both part of a normal single-row variable set. As you can see "Reg start" and "Start" are set to the same date and time, as is "Reg end" and "End". After checking out the item, and then navigating to the Requested items table backend, this is what has been actually registered:

Reg start and Reg end have kept their original value, but the multi-row variables have shifted their values with one hour.

The user timezone has been set to Europe/Stockholm, so I'm expecting that daylight savings time has something to do with this. Has anyone else experienced this, and does anyone know a solution to this problem?

[Hersh D]

If your instance is running on London patch 3 or below, then this could be due to a known issue that's fixed in patch 4. Check here (search for PRB1309233).

Problem	Short Description	Description
Service Catalog PRB1309233	Multi-row variable sets do not work with dates (timezone problem)	Adding a date from a date variable set converts the date. When clicking "Add" on the Date picker, it does a conversion from system timezone to the user timezone, which is wrong as users select date in their timezone and the date selected.

[aymericb]

Hi, 

Similar problem on London Patch 3 : with a table that contains a Date variable and more than one row, all dates are saved with the same value. When i edit date on rows, the modification is replaced by the precedent value.

Regards