1. Home
  2. Forum
  3. Blazor
  4. DateTimePicker with DateTimeOffset

DateTimePicker with DateTimeOffset

Hi,

I’m using Blazor webassembly with .Net5 and Syncfusion.Blazor.Calendars 19.4.0.48.


1) I found an inconsistency when using DateTimePicker with a DateTimeOffset value and ValueChange event. I attached an example page (DateTimeOffsetWithPicker.razor) with two screen print and a project (WasmSfApp).


The first screen print (case 1) is when the user selects a date but no time. The value I’m getting through the ValueChange event is with my browser UTC (+01.00). I picked “05/02/2022 00:00” and get “05/02/2022 00:00:00 +01:00”.


The second screen print (case 2) is when the user selects a time. The value I’m getting through the ValueChange event is without my browser UTC. I picked “05/02/2022 00:30” and get “05/02/2022 00:00:05 +00:00”.


Can you confirm that it is an issue?


2) When I use a DateTimePicker component with DateTimeOffset, I’m expecting that the returned value contains my browser UTC (like case 1).


But, if the value returned doesn’t have my UTC (like case 2), I don’t have any advantage to use DateTimeOffset compared to DateTime. Besides, I will have to add the browser UTC myself when a date is picked.


Therefore, I think the preferred case is case 1 and case 2 should be reported as an issue.

Do you agree with me? Can you report case 2 as the issue and make case 1 the default behavior?


Thanks for your help.

Best regards.

François



Attachment: DateTimePicker_with_offset_ee396be6.zip

4 Replies 1 reply marked as answer
SP Sureshkumar P Syncfusion Team February 3, 2022 01:58 PM UTC

Hi Francois, 

We will validate the requirement in our component. We will update you in two business days (February 8th, 2022).  

Regards, 
Sureshkumar P 


SP Sureshkumar P Syncfusion Team February 8, 2022 01:09 PM UTC

Francois,    

Thanks for your shared information. We have confirmed the reported issue as a bug at our end and this fix will be included in our upcoming patch release, which is expected to be rolled out on February 22nd ,2022.  
You can track the status of this issue from the below feedback.  

Regards,  
Sureshkumar P 


SP Sureshkumar P Syncfusion Team February 23, 2022 08:43 AM UTC

Hi Francois, 

Due to some complexities, we could not include the fix in this week's patch release. We will include it in the upcoming patch release which is expected to be rolled out on March 8th, 2022.  

Regards, 
Sureshkumar P 


SP Sureshkumar P Syncfusion Team March 9, 2022 11:13 AM UTC

Hi Francois, 
We have fixed your reported issue from our end in the latest 19.4.54 version. So, we suggest you upgrade to our latest version to resolve the current issue. 

Regards, 
Sureshkumar P 


Marked as answer
Loader.
Up arrow icon