Enesys RS Data Extension 3.4.7

Fix:

• Fixed a bug with the xmlQuery statement that throws a "Cannot find table 0" exception when querying some resource that returns XML data containing a single node without any child nodes.

Enesys RS Data Extension 3.4.6

Fix:

• Fixed bug introduced in version 3.3.32 that caused in some cases the Reporting Services account to be used instead of the current user credentials when using Windows Integrated Security.

Enesys RS Data Extension 3.4.5

Fix:

• Some modifications of the query designer interface in Business Intelligence Development Studio 2008 R2 prevented the use of the Query Designer. You would end up with a “SplitterDistance must be between Panel1MinSize and Width – Panel2MinSize” error message, and the toolbar buttons were invisible.

Changes:

• The ResultSet selection has been moved from the toolbar to the statement's contextual menus.
  
  The current ResultSet is now displayed as bold:
  
  
  To select the ResultSet, you will now use the "Set as ResultSet" command in the contextual menu:
  

Enesys RS Data Extension 3.4.4

Fix:

A bug when using multivalue parameters with "SqlServerQuery" statements.

Enesys RS Data Extension 3.4.3

New:

• New "sqlServerQuery" statement:
  Starting from version 3.1, you were able to retrieve external SQL Server data by using an xmlQuery statement and a custom ASPX page.
  We have simplified this process by adding a new sqlServerQuery statement that allows you to retrieve data directly from any SQL Server data base.
  

  With the addition of our new “sqlServerQuery” statement things are much more straightforward.

  

   

  This new statement will let you specify a connection string to your database within the integrated query builder as shown in the following screen shot:

  

   

  You can click on the button to the right in order to open the Connection properties dialog box and specify the connection to your own SQL Server Database. Note that you can use the data source credentials for querying the Database without having to store any credentials information within the query itself. We have however let the possibility to enter specific credentials:

  

   

  Finally, you can just specify the SQL SELECT statement that will be used to retrieve data from your SQL Server Database. You can click execute within the Query Designer in order to have a look at the data returned by your query and you can join this data with SharePoint lists by adding some “List” statements:

  

  
   
• New "convertBool" Connection String option:
  In previous versions, SharePoint Boolean fields were retrieved as string column with a value of 0 or 1.
  A new "convertBool" option is now configurable through the Connection String in order to retrieve SharePoint Boolean fields as Boolean data.
  Example:
  Data Source=http://spsdemo;convertBool=true;
  For compatibility reason, the default value of this option is "false".
   
• Intellisense when editing a SqlQuery statement:
  When joining two SharePoint lists, you will usually come up with a query that contains three statements.
  Two list statements used to retrieve data from your SharePoint lists and a sqlQuery statement that will contain an SQL SELECT clause for joining the two SharePoint lists.
  In the previous versions, you don't have much help when writing the SELECT clause. For simple joins, that may not really be a concern, but for more complex SELECT clauses, writing down the field and list names may be a more tedious task.
  This version provides some Intellisense features that will make it unnecessary to look around for column names.
  
• Limiting the number of items returned when designing a query:
  When dealing with very large lists, it may be painful to retrieve all the items when executing your query within the Query Designer just to ensure that the query is correct. A new "Preview limit" option is now available to limit the number of items returned when executing your query within the Query Designer.

Fix:

• The server and client configurations are now deleted when uninstalling the product using Add/Remove Programs.
  In previous versions, you had to use the configuration tools to uninstall the configurations before uninstalling the software to do a clean uninstall.
• A problem inside the NLog file that caused UTF-8 characters not to be shown correctly.
• A bug inside the Query Designer that caused the "Query Statements" panel's theme to not be loaded properly.
• A bug within the Server Configuration tool that caused the program to crash when SQL Server instances/installations had been installed and removed.

Enesys RS Data Extension 3.3.34

New:

• Added support for parameter with itemVersions attribute. If you don't want to return any previous version using a parameter, set the parameter value to "-1".
   

itemVersions attribute - allowed values

Value	Description
-1	No versions will be returned
0	All versions will be returned
a number greater than 0	The specified number of versions will be returned

• Changed the default paging value from 4000 to 2000.

Enesys RS Data Extension 3.3.32

Fix:

• Bug with "File" data type when using itemVersions. It could result in a "Index was outside the bounds of the array" error.
• Bug which prevented the use of "Windows Integrated Security" credentials in some specific cases.
• Bug which prevented the modification of a data source definition in specific cases.

Enesys RS Data Extension 3.3.18

New:

• Added Russian language support in the Query Designer.

Fix:

• bug which prevented to visually edit a query when using an empty URL in the Data Source
• bug introduced in version 3.3.6 which prevented the use of "Windows Integrated Security" credentials in some cases.
• bug that resulted in an unhandled exception when renaming a statement to an already existing tableName
• When updating Enesys RS Data Extension on a server, an IISReset is now done automatically.

Enesys RS Data Extension 3.3.6

New:

• Query Builder integration inside BIDS
  Enesys SharePoint Query Builder is now integrated with Business Intelligence Development Studio.
  This approach brings several advantages over the separate Query Builder available in previous versions:
  
  • No need to re-enter your Data Source properties when building a query.
  • No need to copy/paste/import your query from and to the Query Builder
  • Support for SPLogin credentials
  You have the choice to edit your query using either a Visual Query Builder or an XML editor.
  
  
  The Xml Editor allows the power users to write the query without using a visual interface.
  
  Please note that some features (such as listID or customFields) are not supported by the Visual Query Builder. Therefore, you will be forced to use the XML Editor when using those features.
• New XML editor
  When editing a query that contains syntactic elements not supported by the Visual Query Builder, you will be automatically put in XML editor mode. The XML editor provides intellisense features that simplify query editing. It is possible to toggle between Visual Query Builder and XML mode.
  
  It supports Undo/Redo actions using its contextual menu:
  
  Please note that Visual Studio overrides the “Ctrl+Z” and “Ctrl+Y” behaviors of the Xml Editor, therefore, in some cases you will not be able to use those shortcuts to Undo/Redo an action and it may result in query lost. We advise you to use the contextual menu to Undo and Redo within the editor.
• SQL Editor
  The editor available when editing a SELECT clause within a SqlQuery statement has been improved and offer Undo / Redo commands as well.
  Those who are manipulating big SELECT clauses will be happy to learn that the text is not reformatted anymore each time you edit the query. Your own SQL code layout remains unchanged.
  

Query Builder improvements:

• The Columns/Filtering/Sorting panel displays both the internal and display names of the columns.
  
• A comment can be associated with each statement.
  
• In the Columns panel, columns can now be selected by using the "Space" key for quicker selection.

Enesys RS Data Extension 3.2.16

New features:

• Global variables are available at the DataSource level.
• Filtering the sites that will be used to roll up list's dat awithin a site collection using the new filter element.

Improved features:

• Support for custom fields extending SPFieldLookup which are now managed as Lookup (or LookupMulti if the field can have multiple values) fields.
• Performances improved for rollUpLists statements.

Query Builder Improvements:

Query Builder supports the new 3.2 features (global variables, rollUpLists filter...), and moreover was improved with those functionalities:

• The tool is now available in English and French.
• A new Grid view is available for previewing the result of your query. It provides advanced features such as sorting, grouping, filtering...
• The results can be exported to Excel (Exporting is not available in Evaluation mode)
• When specifying a query condition for a list, it is now possible to select between hidden and non hidden SharePoint columns.
• Any column can be selected for sorting in the Columns/Filtering/Sorting tab. Previously, only selected columns could be used for sorting.
• Support for parameters in the relativeSiteUrl attribute
• The layout can be reset

Enesys RS Data Extension 3.1.301

New: viewScope attribute was added to allow you to configure the selection of items and folders. Valid values are:

Fix: "FilteredLookup" fields are now managed as "Lookup" fields (or "LookupMulti" fields if the field can have multiple values):

• A column containing the ID is added to the result
• Its values can be expanded using the expandMultiValuesColumn attribute

Fix: a bug that was preventing the display of DateTime Calculated columns when they didn't contain any value.

Enesys RS Data Extension 3.1.247

Fix: A bug that was displaying incorrect dates for recurring events when all of these conditions applied:

• A weekly event with the frequency greater than 1
• The first day of the week was different from Monday
• The event occured on several days, and one of its days was the first day of the week.

Enesys RS Data Extension 3.1.245

Fix: the aSiteCollection statement now returns two generated columns:

• SourceUrl: url from which the current site is retrieved
• RelativeSiteUrl: the relative site url to the current site

This allows aSiteCollection statements to be used as source of other statements, such as aSiteColumns, aSitePermissions or aSiteContentTypes.

Fix: Event exceptions will now update any columns (Title, Location, Description, EventType, etc...) instead of updating only dates columns.

Enesys RS Data Extension 3.1.241

Fix: "LookupFieldWithPicker" fields are now managed as "Lookup" fields (or "LookupMulti" fields if the field can have multiple values):

• A column containing the ID is added to the result
• Its values can be expanded using the expandMultiValuesColumn attribute

Enesys RS Data Extension 3.1.239

New features:

• New administrative statements for retrieving administrative data from your SharePoint sites, lists and users:
  
  

  Statement	Description
  aListCollection	Information about lists in the specified sites.
  aListColumns	Information about the columns in the specified lists.
  aListPermissions	Permissions on the specified lists.
  aSiteCollection	Information about specified sites in a site collection.
  aSiteCollectionGroups	Information about site collection's groups
  aSiteColumns	Information about Site Columns in the specified sites.
  aSiteContentTypes	Information about content types available in the specified sites.
  aSitePermissions	Permissions on the specified sites.
  aUserCollection	Information about specified users or users in the specified group.

• New statements mergeLists and rollUpLists. multiList statement is splitted into two separate statements:
  • mergeLists statement replaces the multiList statement where type="MergingList"
  • rollUpLists statement replaces the multiList statement where type="RollUpList"
• Handling large lists using the new paging attribute
• New xmlQuery statement for retrieving XML data either embedded inline or through the specified URL.
• Client and Server Configuration tools for easily configuring both your BIDS and your Report Server.

Improved features:

• Parameter management in Query Builder has been improved.
• Unicode characters (Cyrillic...) are now properly handled in Query Builder.
• Improved stripHtml behavior.

Other modifications:

• Fix: bug when a column's display name contained a colon char and useDisplayName was true.
• Fix: bug when a custom list definition had a template ID greater than 32767.
• Fix: bug when the relativeSiteUrl of a multiList type="RollUpList" was set to "/" or "" and the root site contained the list to roll up.
• The version statement is not supported anymore. The new client and server tools provided enough information for making this statement useless.

Enesys RS Data Extension 3.0.188

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.

Enesys RS Data Extension 2.1.5

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

Enesys RS Data Extension 2.1.4

• 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).

Enesys RS Data Extension 2.1.3

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

Enesys RS Data Extension 2.1.2

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

Enesys RS Data Extension 2.1.1

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

Enesys RS Data Extension 2.1

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

Enesys RS Data Extension 2.0.2

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

Enesys RS Data Extension 2.0.1

• 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 2.0

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.

Enesys RS Data Extension 3.4.7

Fix:

• Fixed a bug with the xmlQuery statement that throws a "Cannot find table 0" exception when querying some resource that returns XML data containing a single node without any child nodes.

Enesys RS Data Extension 3.4.6

Fix:

• Fixed bug introduced in version 3.3.32 that caused in some cases the Reporting Services account to be used instead of the current user credentials when using Windows Integrated Security.

Enesys RS Data Extension 3.4.5

Fix:

• Some modifications of the query designer interface in Business Intelligence Development Studio 2008 R2 prevented the use of the Query Designer. You would end up with a “SplitterDistance must be between Panel1MinSize and Width – Panel2MinSize” error message, and the toolbar buttons were invisible.

Changes:

• The ResultSet selection has been moved from the toolbar to the statement's contextual menus.
  
  The current ResultSet is now displayed as bold:
  
  
  To select the ResultSet, you will now use the "Set as ResultSet" command in the contextual menu:
  

Enesys RS Data Extension 3.4.4

Fix:

A bug when using multivalue parameters with "SqlServerQuery" statements.

Enesys RS Data Extension 3.4.3

New:

• New "sqlServerQuery" statement:
  Starting from version 3.1, you were able to retrieve external SQL Server data by using an xmlQuery statement and a custom ASPX page.
  We have simplified this process by adding a new sqlServerQuery statement that allows you to retrieve data directly from any SQL Server data base.
  

  With the addition of our new “sqlServerQuery” statement things are much more straightforward.

  

   

  This new statement will let you specify a connection string to your database within the integrated query builder as shown in the following screen shot:

  

   

  You can click on the button to the right in order to open the Connection properties dialog box and specify the connection to your own SQL Server Database. Note that you can use the data source credentials for querying the Database without having to store any credentials information within the query itself. We have however let the possibility to enter specific credentials:

  

   

  Finally, you can just specify the SQL SELECT statement that will be used to retrieve data from your SQL Server Database. You can click execute within the Query Designer in order to have a look at the data returned by your query and you can join this data with SharePoint lists by adding some “List” statements:

  

  
   
• New "convertBool" Connection String option:
  In previous versions, SharePoint Boolean fields were retrieved as string column with a value of 0 or 1.
  A new "convertBool" option is now configurable through the Connection String in order to retrieve SharePoint Boolean fields as Boolean data.
  Example:
  Data Source=http://spsdemo;convertBool=true;
  For compatibility reason, the default value of this option is "false".
   
• Intellisense when editing a SqlQuery statement:
  When joining two SharePoint lists, you will usually come up with a query that contains three statements.
  Two list statements used to retrieve data from your SharePoint lists and a sqlQuery statement that will contain an SQL SELECT clause for joining the two SharePoint lists.
  In the previous versions, you don't have much help when writing the SELECT clause. For simple joins, that may not really be a concern, but for more complex SELECT clauses, writing down the field and list names may be a more tedious task.
  This version provides some Intellisense features that will make it unnecessary to look around for column names.
  
• Limiting the number of items returned when designing a query:
  When dealing with very large lists, it may be painful to retrieve all the items when executing your query within the Query Designer just to ensure that the query is correct. A new "Preview limit" option is now available to limit the number of items returned when executing your query within the Query Designer.

Fix:

• The server and client configurations are now deleted when uninstalling the product using Add/Remove Programs.
  In previous versions, you had to use the configuration tools to uninstall the configurations before uninstalling the software to do a clean uninstall.
• A problem inside the NLog file that caused UTF-8 characters not to be shown correctly.
• A bug inside the Query Designer that caused the "Query Statements" panel's theme to not be loaded properly.
• A bug within the Server Configuration tool that caused the program to crash when SQL Server instances/installations had been installed and removed.

Enesys RS Data Extension 3.3.34

New:

• Added support for parameter with itemVersions attribute. If you don't want to return any previous version using a parameter, set the parameter value to "-1".
   

itemVersions attribute - allowed values

Value	Description
-1	No versions will be returned
0	All versions will be returned
a number greater than 0	The specified number of versions will be returned

• Changed the default paging value from 4000 to 2000.

Enesys RS Data Extension 3.3.32

Fix:

• Bug with "File" data type when using itemVersions. It could result in a "Index was outside the bounds of the array" error.
• Bug which prevented the use of "Windows Integrated Security" credentials in some specific cases.
• Bug which prevented the modification of a data source definition in specific cases.

Enesys RS Data Extension 3.3.18

New:

• Added Russian language support in the Query Designer.

Fix:

• bug which prevented to visually edit a query when using an empty URL in the Data Source
• bug introduced in version 3.3.6 which prevented the use of "Windows Integrated Security" credentials in some cases.
• bug that resulted in an unhandled exception when renaming a statement to an already existing tableName
• When updating Enesys RS Data Extension on a server, an IISReset is now done automatically.

Enesys RS Data Extension 3.3.6

New:

• Query Builder integration inside BIDS
  Enesys SharePoint Query Builder is now integrated with Business Intelligence Development Studio.
  This approach brings several advantages over the separate Query Builder available in previous versions:
  
  • No need to re-enter your Data Source properties when building a query.
  • No need to copy/paste/import your query from and to the Query Builder
  • Support for SPLogin credentials
  You have the choice to edit your query using either a Visual Query Builder or an XML editor.
  
  
  The Xml Editor allows the power users to write the query without using a visual interface.
  
  Please note that some features (such as listID or customFields) are not supported by the Visual Query Builder. Therefore, you will be forced to use the XML Editor when using those features.
• New XML editor
  When editing a query that contains syntactic elements not supported by the Visual Query Builder, you will be automatically put in XML editor mode. The XML editor provides intellisense features that simplify query editing. It is possible to toggle between Visual Query Builder and XML mode.
  
  It supports Undo/Redo actions using its contextual menu:
  
  Please note that Visual Studio overrides the “Ctrl+Z” and “Ctrl+Y” behaviors of the Xml Editor, therefore, in some cases you will not be able to use those shortcuts to Undo/Redo an action and it may result in query lost. We advise you to use the contextual menu to Undo and Redo within the editor.
• SQL Editor
  The editor available when editing a SELECT clause within a SqlQuery statement has been improved and offer Undo / Redo commands as well.
  Those who are manipulating big SELECT clauses will be happy to learn that the text is not reformatted anymore each time you edit the query. Your own SQL code layout remains unchanged.
  

Query Builder improvements:

• The Columns/Filtering/Sorting panel displays both the internal and display names of the columns.
  
• A comment can be associated with each statement.
  
• In the Columns panel, columns can now be selected by using the "Space" key for quicker selection.

Enesys RS Data Extension 3.2.16

New features:

• Global variables are available at the DataSource level.
• Filtering the sites that will be used to roll up list's dat awithin a site collection using the new filter element.

Improved features:

• Support for custom fields extending SPFieldLookup which are now managed as Lookup (or LookupMulti if the field can have multiple values) fields.
• Performances improved for rollUpLists statements.

Query Builder Improvements:

Query Builder supports the new 3.2 features (global variables, rollUpLists filter...), and moreover was improved with those functionalities:

• The tool is now available in English and French.
• A new Grid view is available for previewing the result of your query. It provides advanced features such as sorting, grouping, filtering...
• The results can be exported to Excel (Exporting is not available in Evaluation mode)
• When specifying a query condition for a list, it is now possible to select between hidden and non hidden SharePoint columns.
• Any column can be selected for sorting in the Columns/Filtering/Sorting tab. Previously, only selected columns could be used for sorting.
• Support for parameters in the relativeSiteUrl attribute
• The layout can be reset

Enesys RS Data Extension 3.1.301

New: viewScope attribute was added to allow you to configure the selection of items and folders. Valid values are:

Fix: "FilteredLookup" fields are now managed as "Lookup" fields (or "LookupMulti" fields if the field can have multiple values):

• A column containing the ID is added to the result
• Its values can be expanded using the expandMultiValuesColumn attribute

Fix: a bug that was preventing the display of DateTime Calculated columns when they didn't contain any value.

Enesys RS Data Extension 3.1.247

Fix: A bug that was displaying incorrect dates for recurring events when all of these conditions applied:

• A weekly event with the frequency greater than 1
• The first day of the week was different from Monday
• The event occured on several days, and one of its days was the first day of the week.

Enesys RS Data Extension 3.1.245

Fix: the aSiteCollection statement now returns two generated columns:

• SourceUrl: url from which the current site is retrieved
• RelativeSiteUrl: the relative site url to the current site

This allows aSiteCollection statements to be used as source of other statements, such as aSiteColumns, aSitePermissions or aSiteContentTypes.

Fix: Event exceptions will now update any columns (Title, Location, Description, EventType, etc...) instead of updating only dates columns.

Enesys RS Data Extension 3.1.241

Fix: "LookupFieldWithPicker" fields are now managed as "Lookup" fields (or "LookupMulti" fields if the field can have multiple values):

• A column containing the ID is added to the result
• Its values can be expanded using the expandMultiValuesColumn attribute

Enesys RS Data Extension 3.1.239

New features:

• New administrative statements for retrieving administrative data from your SharePoint sites, lists and users:
  
  

  Statement	Description
  aListCollection	Information about lists in the specified sites.
  aListColumns	Information about the columns in the specified lists.
  aListPermissions	Permissions on the specified lists.
  aSiteCollection	Information about specified sites in a site collection.
  aSiteCollectionGroups	Information about site collection's groups
  aSiteColumns	Information about Site Columns in the specified sites.
  aSiteContentTypes	Information about content types available in the specified sites.
  aSitePermissions	Permissions on the specified sites.
  aUserCollection	Information about specified users or users in the specified group.

• New statements mergeLists and rollUpLists. multiList statement is splitted into two separate statements:
  • mergeLists statement replaces the multiList statement where type="MergingList"
  • rollUpLists statement replaces the multiList statement where type="RollUpList"
• Handling large lists using the new paging attribute
• New xmlQuery statement for retrieving XML data either embedded inline or through the specified URL.
• Client and Server Configuration tools for easily configuring both your BIDS and your Report Server.

Improved features:

• Parameter management in Query Builder has been improved.
• Unicode characters (Cyrillic...) are now properly handled in Query Builder.
• Improved stripHtml behavior.

Other modifications:

• Fix: bug when a column's display name contained a colon char and useDisplayName was true.
• Fix: bug when a custom list definition had a template ID greater than 32767.
• Fix: bug when the relativeSiteUrl of a multiList type="RollUpList" was set to "/" or "" and the root site contained the list to roll up.
• The version statement is not supported anymore. The new client and server tools provided enough information for making this statement useless.

Enesys RS Data Extension 3.0.188

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.

Enesys RS Data Extension 2.1.5

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

Enesys RS Data Extension 2.1.4

• 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).

Enesys RS Data Extension 2.1.3

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

Enesys RS Data Extension 2.1.2

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

Enesys RS Data Extension 2.1.1

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

Enesys RS Data Extension 2.1

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

Enesys RS Data Extension 2.0.2

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

Enesys RS Data Extension 2.0.1

• 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 2.0

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.