Forums Home / Spread / Spread for ASP.NET (Web Forms)
Posted by: anh.pham on 19 April 2023, 4:15 am EST
anh.pham
Posted 19 April 2023, 4:15 am EST - Updated 19 April 2023, 4:52 am EST
Dear Sir/Madam,
We got an issue with the datetime format. Namely, on the SpreadSheet we input the data 0:00 the SpreadSheet auto formatter that value with display text 0:00, and the value is 1899/12/30 then we export the SpreadSheet to Excel. That cell will get an issue with the format. Please kindly refer to the capture below
ankit.kumar
Posted 23 April 2023, 5:09 pm EST - Updated 23 April 2023, 5:14 pm EST
Hi Anh,
Apologies for the late reply. I tried with the latest version of SpreadJS, however, I was unable to replicate the issue at my end.
After setting the value “0:00” in the cell, the value shown in the formula bar is “12:00:00 AM” which is expected.
Microsoft Excel is a native application and has access to system culture and datetime format. When an excel file is open, it shows the dateTime format defined by the system.
I suspect the issue might be occurring because of the dateTime format defined by the system.
You could refer to the following gif that shows the steps we have followed for testing. You could observe that Excel shows the values depending on the format defined by the system. You could check the culture and formats defined by the System.
You could also define the custom culture in the SpreadJS. Kindly refer to the following demo for more details: https://www.grapecity.com/spreadjs/demos/features/culture/globalization/purejs
Create Custom Culture Docs: https://www.grapecity.com/spreadjs/docs/features/culture/culturecustom
Regards,
Ankit
anh.pham
Posted 24 April 2023, 2:23 am EST
Dear Ankit,
I am glad to receive your response. As per your description, it belongs to the system format, but I follow the region format from the gif it is the same as you. Please kindly refer to the zip below.
Best & regard,
Anh Pham
demo region.zip
ankit.kumar
Posted 25 April 2023, 8:04 am EST
Dear Anh,
I could see the issue with the video that you have shared with me. However, I was unable to replicate the issue at my end. I am setting up a new machine and will try on the new machine too with the region and formatters applied as seen in the video.
This will take some time at my end, however, I will let you know as soon as I am finish setting up the machine and testing at my end.
Regards,
Ankit
ankit.kumar
Posted 26 April 2023, 11:55 pm EST
Dear Anh,
I created a new virtual machine and still I was unable to replicate the issue at my end with the new VM. The County/Region at my end is “United States” and the Regional Fomrat at my end is "English (United States) as earlier shown in the gif.
Would it be possible for you to check on any other machine at your end? I downloaded the Virtual Machine at my end using the following link: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
Could you also try out using a new virtual machine and check if the issue still persists at your end? Or you could change the Regional settings of the VM to replicate the issue at your end and share the setting with us.
Kindly let me know about your findings so that we could further investigate the issue you are facing.
Regards,
Ankit
ankit.kumar
Posted 30 April 2023, 6:40 pm EST
Hi Anh,
Thanks for sharing the information on the time zone. I was able to replicate the issue at my end when the time zone is set to “(UTC + 07:00) Bangkok, Hanoi, Jakarta”.
I could see the issue with the “Microsoft Edge” and “Chrome” Browsers. However, for FireFox Browser, it seems to be working fine. I have escalated this to the dev team for further investigation. The internal tracking id for this issue is: SJS-18103. I will let you know when there is an update from the dev team. Currently, I couldn’t find a workaround to tackle this issue.
I have tested with the following Browser Versions:
Microsoft Edge Version: Version 112.0.1722.58 (Official build) (64-bit)
FireFox Version: 112.0.2 (64-bit)
Operating System: Windows 10 Pro (64 bit)
Regards,
Ankit
ankit.kumar
Posted 5 May 2023, 2:03 am EST
Hi Anh,
This issue is confirmed as a bug and the devs are working on the fix. I will let you know when there is an update for you or when the issue has been fixed.
Regards,
Ankit
anh.pham
Posted 5 May 2023, 2:09 am EST
Dear Ankit,
I’m glad to hear good news from you, hope this issue will be solved soon.
Thanks a lot
Best & Regards
Anh Pham
ankit.kumar
Posted 14 May 2023, 11:17 pm EST
Dear Anh,
This bug will be fixed in the SpreadJS V16.1.1. which is expected to be released by the next week. I will let you know when the release will be available.
Regards,
Ankit
anh.pham
Posted 14 May 2023, 11:22 pm EST
Dear Ankit,
I appreciate your support.
Regards,
Anh Pham
ankit.kumar
Posted 21 May 2023, 11:32 pm EST
Hi Anh,
The mentioned issue with internal tracking id SJS-18103 has been fixed in the latest version of SpreadJS V16.1.1. Kindly upgrade to the latest version of SpreadJS. You may download the latest version using the following link:
http://cdn.grapecity.com/spreadjs/16.1.1/Files/SpreadJS.Release.16.1.1.zip
Please let us know if you still face any problems.
Regards,
Ankit
