Our use of cookies

We use cookies to tailor your experience, gather analytics, and provide you with live assitance. By clicking "Accept" or continuing to browse our site you agree to the use of cookies. For more details please read our Cookie Policy.

Accept

Popular articles

SQList version history

Download a previous version of SQList

How do I install or upgrade AxioWorks SQList?

Configure authentication methods to SharePoint

Security Considerations for Installing SQList

More support options:

Use the search page;

Email us at support@axioworks.com;

Send us a message using the Contact Us page.

What is new in SQList ver. 6.0.4.0

Version 6.0.4.0 of SQList is a minor update; you can therefore upgrade for free if you have a licensed version 6.x. To download the latest version of SQList visit http://www.axioworks.com/sqlist-download/

There are no breaking changes in this release.

See below a summary of the changes.

Fixed handling of date and time columns in local time and daylight saving time


Internally, SharePoint stores "Date Only" and "Date and Time" columns as UTC values in "datetime" columns.

Because of that, a "Date Only" value of "15 Dec 2018" would be stored as "2018-12-15 00:00:00"; that if the value were stored using a SharePoint site with a GMT regional setting.

If the site had a GMT+1 regional setting, the value stored would be "2018-12-14 23:00:00" (11pm of the day before).

SQList, by default, exports "Date Only" and "Date and Time" as GMT values and that can cause a problem with "Date Only" values as, in the GMT+1 example, the value exported would be "2018-12-14" (the day before) once the time portion is dropped.


By disabling the option "Export Datetime values UTC", SQList applies the time zone correction to the value. In the GMT+1 case it would add one hour to the value and bring it back to its original "2018-12-15 00:00:00", so that after dropping the time portion the value "2018-12-15" would be correct.

An additional complication arises when the value stored is withing the Daylight Saving Time period, because in the GMT+1 case the value stored would then be "2018-12-14 22:00:00" (10pm of the day before). In the GMT+1 case, the +1 hour correction would not be enough and the resulting value would again be "2018-12-14" (the day before) once the time portion is dropped.

In this update, we have fixed this issue so that the correct values are exported, no matter the regional settings and Daytime Saving Time.

See below some screenshots that demonstrate the correct behaviour. 








Note: In the SQList replication, the "Recipes" list has the "Export Datetime values UTC" option selected while "Food ingredients" list has it unselected.





More can be read online, here are a few links:



Reinstated support for SharePoint 2010


We have modified our libraries so that SharePoint 2010 is supported again. In our previous version we used upgraded some of the libraries and lost compatiblity with SharePoint 2010.



If you have any questions about this upgrade, please contact us at support@axioworks.com