We have changed the way SQList resyncs a table when the corresponding list's structure changes. While in previous versions SQList was only re-checking the items for a change in the item's version, it now updates the entire row therefore forcing the population of new columns added to the list.
Note that for this action to take place you need to enable the "Force data re-sync on list structure change" option in Global Settings.
Better backward compatibility with version 5
We have enhanced the backward compatibility with version 5. This is useful when you upgrade from version 5 to 6 but want to keep the version 5 format for SQL table and columns names.
We added two new options in Global Settings:
- Use version 5 clean names: selecting this option makes SQList use the same algorithm used by version 5 to generate table and column names.
- Use the "ID" column as Taxonomy term key: selecting this option makes SQList use the "ID" column (of type INT in SQL) as unique key for a taxonomy term, rather than the "TermGuid" column (of type UNIQUEIDENTIFIER in SQL).
Filter to exclude system lists and columns 
We have added more filters to exclude SharePoint system lists and column from the export. "SharePoint system lists and column" are those lists and columns that SharePoint automatically create in web sites and lists, and contain data that are of no use to an organisation. Apart for the fact that exporting these lists takes unnecessary resources, they often do not have conventional structures that can be exported to a normalised SQL table. For new installations these filters are already initialised with the most common scenarios for SharePoint version 2010, 2013, 2016, and OnLine.
IF INSTEAD YOU ARE UPGRADING FROM A PREVIOUS VERSION, we recommend that you update the following Global Settings:
Always accepted fields for list
Replace the entire content with:
ContentType,ContentTypeId,_UIVersion,_UIVersionString,Author,Created,Editor,GUID,Modified,owshiddenversion,Title,UniqueId,FileRef,_ModerationStatus,EMail,Name
Always accepted fields for document libraries
Replace the entire content with:
BaseName,EncodedAbsUrl,File_x0020_Type,regex:^_dlc_DocId
Always refused fields for lists
Replace the entire content with:
regex:^_,FileLeafRef,FileType,CatchAllData,CatchAllDataLabel,regex:^Path[0-9]+$,regex:^Term[0-9]+$,SPSPictureTimestamp,SPSPicturePlaceholderState,SPSPictureExchangeSyncState,regex:^Link.+TitleNoMenu$,regex:^Link.+Title[0-9]*$,ImnName,regex:^PictureOnly_Size_[0-9]+px$,NameWithPictureAndDetails,EditUser,UserSelection,ContentTypeDisp,regex:^HTML_
Important: ensure that you add any custom settings that you may have in your settings.
This is how your settings should look like at the end:
This is a possible breaking change: SQList will remove system lists and columns from your current replications and therefore from the corresponding SQL tables.
This will cause issues if:
- you are using data contained in system columns;
- you are using those tables in views with schemabinding.
Both cases are highly unusual.
Removed AppId/AppPassword limitations
We have removed the following limitation with AppId/AppPassword authentication:
This is a possible breaking change: SQList will change the name of foreign key column in the many-2-many tables corresponding to the multi-lookup columns.
Handling of "Expired change token detected"
We have enhanced the detection of expired tokens, SQList is now able to automatically recover and realign the synchronisation between SQL tables and change tokens.
Minor changes and fixes:
- Changed item check to use version number rather than modified date;
- Fixed issue with columns with special characters;
- Fixed error with missing FileRef column;
- Fixed issue with case-sensitive collations in SQL databases;
- Fied issue with duplicate web GUIDs in different site collections.