Date/Time field in Multi-Row Variable Set not capturing correct time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-09-2019 02:06 PM
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?
- Labels:
-
Service Portal Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-09-2019 03:25 PM
There seems to be some problem with your date /time format settings in system .
Go and check whether the valid date format is set or not
System properites --> System ---> Date Format
it should be something like below yyyy-MM-dd and time like HH:mm:ss
Note : incase they are set right then do check if the format of date/time has not been changed for that Multi row variable
For ref: Go through the below link where same issue occured
https://community.servicenow.com/community?id=community_question&sys_id=d3eff2eddb58dbc01dcaf3231f96199b
Mark my ANSWER as CORRECT and HELPFUL if it helped
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-10-2019 02:03 AM
I've checked the system properties, everything is set correctly. Wrong settings would probably also affect the single-row variables, which behaves a expected, not only the multi-row variables. But what do you mean by checking if the time/date format has been changed for the multi-row variable?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-10-2019 03:40 AM
Do check the if some setting has been done in default value for that field if yes then remove it
Refer the below link for reference
https://community.servicenow.com/community?id=community_question&sys_id=408583eddbd8dbc01dcaf3231f961958
Mark my ANSWER as CORRECT and HELPFUL if it helped.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 05:16 AM
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. |