New features:

• SQL Engine for manipulating SharePoint lists using SQL statements.
  
• Support for multivalue parameters.
• In and NotIn CAML Query operators.
  
• IfNot element in Eq operator to retrieve either all items or items filtered on a specific value. 
  
• Querying over multiple SharePoint Web Applications by specifying an empty server url and a full url in the relativeSiteUrl attribute.
• Logging framework for retrieving errors, debug and trace info.
• Query Builder for visually building queries.
  
• Installation program for installing or updating Enesys RS Data Extension more easily.
• Retrieving all non-hidden fields by specifying '*' (star) in the fields element.
• timeZone attribute for retrieving correct dates in item's versions.
  

Improved features:

• New Automatic mode for retrieving recurring and non-recurring events.
  
• Rolling up list's items over multiple lists using elevated privileges.
• Syntax validation enhanced and more meaningful error messages.
• resultSet statement not mandatory anymore (data returned by the latest statement will be used).
• webCulture attribute not necessary anymore when retrieving item's versions.

• Fix: a bug was preventing RichText values not containing any HTML tags to display properly when setting the stripHtml attribute to true.
• Fix:  distinct operation may return duplicated values when the source data set contains the same value written using different letter case.
• Fix: When applying a distinct operation on multiple columns using a descending sort order, only the latest column would be sorted in descending order. Other columns are sorted in ascending order.
• Improved: various improvements have been made to the way Html is stripped out from rich text values when using the stripHtml attribute. This should result in less undesired blank lines. This change might affect your existing reports. 
• Case-Sensitivity in distinct operation
  A new option has been added to the distinct operation for allowing to get distinc values in a case insensitive way:
  

  When setting caseSensitive value to false, a case-insensitive comparaison will be performed over string values. For compatibility with previous versions, the default value of the caseSensitive element is true.

• Fix: error on date parsing when using itemVersions attribute for retrieving versions of list items in some specific cases.
  
  Background info:
  The SharePoint Web Service available for retrieving item versions is not only limited to retrieve versions for one column at a time, it also does not return data in an invariant format (data format will depend on the regional settings of a site).
  Though it is possible to retrieve site language using SharePoint web services, it is not currently possible to retrieve site's regional settings. 
  Therefore, when retrieving item versions from a site using regional settings with date and number format different from the default site language settings, you will get some error on parsing date values.
  
  Solution:
  In order to work around this problem, our only solution was to provide a new attribute for specifying the culture of the web site from which list's data are retrieved as shown in the following image:
  
  When provided, Enesys RS Data Extension will use the culture provided by this attribute for parsing item (previous) version's values. When this attribute is not defined, the default culture of the site will be used (based on the site language).

• The 5000 items limitation as well as the randomly tagged row using "evaluation version x days left" have been removed when running Enesys RS Data Extension in evaluation mode.

• Fix: Due to some bug in the build process, one of the component used for Enesys RS Data Extension final assembly was compiled in debug mode. This resulted in the creation of an xml file named XmlTest.xml. Though this may not be a big concern when running reports within the report designer, this may lead to security concerns on the server side where the permissions may not allow the creation of this file and thus throwing an error.
  This bug was introduced in version 2.1.1 and does not affect previous versions.

• Fix: a bug was preventing support for full precision of large numbers entered into SharePoint columns of type "Number".
• Fix: When rolling up list items using "multiList" statement, the rstLabel column is supposed to contain the relative site url of the list to which the item pertains. As the result of a bug, the rstLabel column was initialized with the tableName attribute of the multiList statement for the first list to be rolling up.
• Fix: The schema files provided in the 2.1 package had not been updated for providing support for the following attributes : itemVersions and meetingInstanceId. The Schema files available in 2.1.1 package have been updated. You just need to replace your current files with the new ones. See the documentation for more information about schema files installation.

• Lookup and Person or Group ID
  SharePoint “Lookup” and “Person or Group” columns will now have two columns in the resulting dataset made available to Reporting Services for holding both the actual value and the target item ID. This new approach makes it possible to join lists based on the ID rather than the actual lookup value which may not always be unique.
• Attachments
  Rather than the number of attachments, the “Attachments” column now returns the list of attachments url separated by a comma.
  You can set the expandMultiValuesColumn attribute to “Attachments” for duplicating items with multiple attachments and making it possible to display each attachment individually within Reporting Services (a sample report provided with the package demonstrates how to do this).
• UserInfo list
  It is now possible to retrieve site collection user information by specifying “UserInfo” as the title attribute’s value of a list query element.
  It may be especially useful when you would like to get more detailed information about users assigned to list items using a “Person or Group” column.
• Item versions
  It is now possible to retrieve item versions for lists for which you have enabled versioning.
• Meeting instances
  In versions 2.0.x and earlier of Enesys RS Data Extension, retrieving data from lists part of a recurring meeting workspace would only retrieve items for the current event (the next event occurring).
  Starting from version 2.1 it is possible to retrieve items for all occurrences or even items for a specific occurrence.
   
• Fixed a compatibility issue with Wss V2 multiple values "Choice" column.

• Fix: when both useDisplayName attribute was set to true and xmlns=http://enesyssoftware.com/schemas schema was specified in the root element, FieldRef name values within the query element were not replaced by their "internal name" counterpart.
• Fix: Site collection admin permissions were necessary when running a multiList query of type RollUpList. The approach used to collect child sites has been changed. However you have to be aware of the following limitations:
  
  Only one set of credentials is used for communicating with the SharePoint server. Thus, it is still necessary for the account used to run the report to have SharePoint "Browse Directories" permission for being able to enumerate child sites for a specific site.
  If the account doesn't have this permission for a specific site, it will not be able to roll up data from a list within a child site though it might have the necessary permissions to retrieve the items from the list.
  For this reason, the multiList query element of type "RollUpList" is not the perfect tool for rolling up data only available to the current user running the report (using Windows Integrated security).
  We are thinking of several possible approaches to overcome the current limitation in future versions.
• Fix: "Carriage return" characters in Multiple lines of text SharePoint columns are not replaced by whitespace anymore.

• Bug fix - joining two result sets resulting from a multiList query element was throwing the following error:  "A DataTable named '[relativeURLof subsite]' already belongs to this dataset."

Enesys RS Data Extension version 2.0 is not compatible anymore with SharePoint 2003. Please note also that support for SQL Server Reporting Services 2000 has been discontinued. Enesys RS Data Extension 2.0 will only install on SQL Server Reporting Services 2005.

• new rowLimit attribute for returning only the n first element
• schema files provided for intellisense and validation support.
• support for SharePoint 2007 recurring events options as well as events exceptions.
• relativeSiteUrl attribute for the list element may be now specified using a report parameter.
• Support for retrieving items from a specific folder.
• Possibility to specify a custom separator for multiple values columns.
• Possibility to expand multiple values columns so that it is possible to group on this column.
• Possibility to specify a sort order for the "Distinct" operation.
• Possibility to roll-up lists within an entire site collection.
• Possibility to retrieve list collection, list permissions, web permissions and SharePoint groups from a site or a set of sites.
•  xml comments are now supported within queries.

• Fixes a bug that was preventing recurring events from being expanded when used with Moss 2007/ Wss V3. Stil, there are some limitations with Moss 2007/Wss V3 recurring events new features. See the knowledge base for more details.

• Increased timeout for large SharePoint lists support

• Bug fix - "union" operation.  childTableName items were returned twice in the resulting result set.

• New optionnal listID attribute for specifying SharePoint list by its GUID rather than its title.
• New attributes for expanding recurring events from SharePoint event lists.
• New stripHtml attribute for stripping html tags from SharePoint fields containing html tags.
• New customFields element for adding custom columns holding running values.
• New "select" operation for selecting a subset of a result set.
• Bug fix - "union" operation would not work in some cases with lists having the same fields ordered differently.

• New listCollection query element for retrieving list collection for a site or a set of sites.
• New listPermissions query element for retrieving permissions for a specific list.
• New webPermissions query element for retrieving permissions given at the site level through site groups (roles).
• New webGroups query element for retrieving cross-site groups for a site or a set of sites.
• New version query element for displaying Enesys RS Data Extenion edition and version.

• New resultSet element for specifying the result set used as the report Dataset.

  With prior versions of Enesys RS Data Extension, it was necessary to give the value "results" to the dstTableName element of an sqlOp operation to let ERSDE knows that it should be used as the report Dataset. As noted by some customers, this approach is not very practical when dealing with complex queries where it might be necessary to switch from the result of one operation to the other for tests purposes.

  Setting dstTableName to "results" is not necessary anymore. Instead, you can define a resultSet element. The value of this element should be the name of the operation or list whose data should be used as the report Dataset.

  The following image shows the syntax used with versions prior to 1.2. A distinct operation is applied to the Issues SharePoint list named "Components" within the query (tableName attribute). To let ERSDE knows that the report Dataset will consist of the data resulting from the "distinct" operation (keep in mind that you may have several sqlOp operations within a query), the dstTableName element must be given the value "results".

  
  

  The following image shows the new syntax used in version 1.2. Note that you can give a meaningful dstTableName to the "distinct" operation as the resultSet element is used to tell Enesys RS Data Extension which result set to use as the report Dataset.

  This approach has the clear advantage to let you easily switch from a result set to another. As an example, you could set the value of resultSet to "components" and rerun the query to retrieve data from the Issues list. With the previous syntax, it would have been necessary to change dstTableName value to something else than "results" and change "tableName" attribute to "results".

  

• New optional moderationType attribute for list element.

  This attribute makes it possible to retrieve pending items from approved lists or document libraries. The possible values are Moderator and Contributor.

  Please not that the account under which the report is running will need the necessary SharePoint permission on the list in order to retrieve all the pending items.

• Improved error messages.

  We have improved error message to make it easier to localize problems when building complex queries. 
  When you run a query, you will now get a meaningful message when a sqlOp operation is missing parameters, a table name used in operation does not exist, a joining columns used in operation does not exist, etc..

• When credentials are stored securely in the report server, it's now possible to check "Use as Windows credentials when connecting to the data source". This was not the case with the previous version. Please note however that it is not necessary to check this option as network credentials will be used anyway to connect to SharePoint Web Services.

• "Windows Integrated security" option works now as expected. The credentials of the user running the reports will be passed to SharePoint Web Services. If the user doesn't have the necessary rights for the SharePoint lists, he will not be able to display the data.

• When using "Credentials supplied by the user running the report" option or "Credentials stored securely in the report server" without checking "Use as Windows credentials when connecting to the data source", it is now possible to prefix the account with the domain name (eg: domain\login).