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.

What is new in SQList ver.

What is new in SQList ver.

Version 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.

Additional SharePoint authentication methods

We have added the following methods of authentication to SharePoint:

  • Azure AD Applications permissions authentication;
  • Azure AD Delegated permissions authentication;
  • Forms authentication.
For full details about SharePoint authentication methods supported by SQList, see the support article: Configure authentication methods to SharePoint

Feature to request re-sync of SQL tables from SQList Manager

We have added a new feature to request full re-synchronisations of SQL table directly form SQList Manager. Until now, this operation required running of TSQL scripts directly in the destination database.

To re-sync a table, select the Replications option in SQList Manager:

Note: the SQList Service must be stopped before performing this operation.

Click the Tables icon corresponding to the replication that own the SQL table you wish to re-synchronise. This will open a pop-up with the list of all tables currently existing in the destination database for that replication:

For each table you wish to re-sync, you can choose one of three options:

  • Check existing row: will compare the version of each item in the SharePoint list with the version of its corresponding row in the SQL table and update the SQL row only if the versions are different.
  • Re-synchronise all rows: will update ear row in the SQL table with its corresponding SharePoint list item, regardless of whether their versions are different or not. Extra and missing rows in the SQL table will also be removed and added accordingly. This is useful when a new column is added to a list with a default value and you want to fill it in the SQL table.
  • Drop an rebuild table: this option will drop the table (and all multi-lookup related tables) and recreate them from scratch.
Once you have selected the table to re-synchronise, click the "Request re-synchronisation" button to initiate it, then start the SQList Service.

Reset setting to inherit from parent setting

It is now possible to reset a setting value to inherit for it's parent setting. This is useful when you need to remove a custom setting and set it to its default/parent's value.

All settings (except Global settings) have a "reset" icon next to them, as shown in the image below.

Use Internal Name instead of Static Name

We have change the way SQList generates SQL column names to use the column's Internal name rather than its Static name, the reason being that the use of the static name created "duplicate column" issues under certain circumstances.

Static names are the name used across the entire SharePoint site, while Internal names are assigned to list's columns and are unique within that list.

E.g.: if you have a Site column named "MyColumn" and you assign it to a list that already containsList column named "MyColumn" the names in the list will be:

Site column: Static name: "MyColumn", Internal name: "MyColumn0"
List column: Static name: "MyColumn", Internal name: "MyColumn"

Using the Static names will cause duplicates.

Note: The name displayed in the URL when editing a column is the Internal name:

We have added a new Global Setting to control this behaviour and set it to use Internal names by default:

Important: if you are upgrading SQList, the upgrade will set this setting in your existing replications to use Static names to keep compatibility with your current SQL tables. New replication will use the Internal name.

Minor changes and fixes:

  • fixed support for TLS 1.2;
  • Improved handling of expired change tokens;
  • fixed issue with duplicate database connection;
  • fixed two bugs.