1
1
The perfect solution for creating powerful yet inexpensive business solutions by integrating data from multiple SharePoint lists. Enesys RS Data Extension lets you leverage all the power of Microsoft SQL Server Reporting Services with your SharePoint Data.

Enesys RS Data Extension 3.9

New Features

SharePoint 2013 Compatibility

Enesys RS Data Extension is now compatible with SharePoint 2013. It can be installed in SharePoint Integration Mode, is available as a data source type and will use SharePoint object model (unless you configure it another way).

Data Source configuration under SharePoint 2013.

Visual Studio 2012 Shell Compatibility

When it was initially released, SQL Server 2012 Data and Business Intelligence Tools (formerly known as BIDS and renamed to SSDT) were running under Visual Studio 2010 shell. For those not used to this usual visual studio shell shift, this could be somewhat confusing due to the 2012 naming.

Earlier this year, Microsoft released SQL Server Data Tools and Business Intelligence for Visual Studio 2012 (see blog announcement).

Enesys RS Data Extension 3.9 is now compatible Visual Studio 2012 shell version.

Both Shell versions can be installed side by side. Therefore, Enesys RS Client Configuration will distinguish each version by specifying the Shell being used like shown in the following screen shot:

Enesys RS Client Configuration tool - SSDT 2012 for both VS 2010 and VS 2012 shell are configured.

Report using Enesys RS Data Extension data source within Visual Studio 2012 shell:

Visual Studio 2012 Shell - Reporting Services Report Designer

Support for Multi-Value Parameters within the Query Designer

Even though Enesys RS Data Extension queries support multi-value parameters (using “IN” clause either at the list level or within a SqlQuery statement), it was only possible to pass a single parameter values when previewing (executing) the query within the query designer:

Filtering using a multi-value parameter.

This is not really a big concern if you consider that you can preview the report within the report designer and therefore pass multiple values through regular report execution (which is often easier if your report parameter get its values from another query).

running a report that uses a multi-value parameter.

However to make it easier to test an individual query, it is now possible to pass multiple values directly within the query designer by using a comma to separate each value like shown in the following screen shot:

Entering parameter values when running a query within the query designer.

Multi-value Lookup and Projected Fields

Starting from SharePoint 2010, it is possible to select additional fields in a lookup target list (a projection). Amongst other things, you will be able to display (through views) those fields as if they were part of your list.

Lookup Fields projection.

When expanding a multi-value lookup column (see the screen shot below) – meaning breaking down multiple values into single value by duplicating each item as if you were doing a join between the item and the lookup values - , Enesys RS Data Extension 3.8 and earlier will just duplicate projected fields value like with any other fields instead of retrieving the value that matches the single lookup value.

Expland multi-values column.

Enesys RS Data Extension 3.9, provides support for projected fields and will automatically extract the single value that matches the lookup value item.

Projected Fields are properly expanded in Enesys RS Data Extension 3.9.

Send Technical Data and Error Log the Easy Way

Because Enesys RS Data Extension supports Reporting Services 2005, 2008, 2008R2 and 2012 as well as SharePoint 2007, 2010 and 2013, it’s always tricky for the support team to get the necessary customer configuration information without trying to guess or exchanging several emails.

In order to make things much easier in that area, Enesys RS Client Configuration and Enesys RS Server Configuration tools now offer an option to prepare technical data and error log information in a zip file that can be sent to our support.

Enesys RS Client Configuration - Save Debug Info.

When clicking on Save Debug Info button you will be proposed to specify the name of a zip file that will contain various files that will provide our support valuable information for providing assistance (error log and configuration data).

Enesys RS Data Extension 3.9

New Features

SharePoint 2013 Compatibility

Enesys RS Data Extension is now compatible with SharePoint 2013. It can be installed in SharePoint Integration Mode, is available as a data source type and will use SharePoint object model (unless you configure it another way).

Data Source configuration under SharePoint 2013.

Visual Studio 2012 Shell Compatibility

When it was initially released, SQL Server 2012 Data and Business Intelligence Tools (formerly known as BIDS and renamed to SSDT) were running under Visual Studio 2010 shell. For those not used to this usual visual studio shell shift, this could be somewhat confusing due to the 2012 naming.

Earlier this year, Microsoft released SQL Server Data Tools and Business Intelligence for Visual Studio 2012 (see blog announcement).

Enesys RS Data Extension 3.9 is now compatible Visual Studio 2012 shell version.

Both Shell versions can be installed side by side. Therefore, Enesys RS Client Configuration will distinguish each version by specifying the Shell being used like shown in the following screen shot:

Enesys RS Client Configuration tool - SSDT 2012 for both VS 2010 and VS 2012 shell are configured.

Report using Enesys RS Data Extension data source within Visual Studio 2012 shell:

Visual Studio 2012 Shell - Reporting Services Report Designer

Support for Multi-Value Parameters within the Query Designer

Even though Enesys RS Data Extension queries support multi-value parameters (using “IN” clause either at the list level or within a SqlQuery statement), it was only possible to pass a single parameter values when previewing (executing) the query within the query designer:

Filtering using a multi-value parameter.

This is not really a big concern if you consider that you can preview the report within the report designer and therefore pass multiple values through regular report execution (which is often easier if your report parameter get its values from another query).

running a report that uses a multi-value parameter.

However to make it easier to test an individual query, it is now possible to pass multiple values directly within the query designer by using a comma to separate each value like shown in the following screen shot:

Entering parameter values when running a query within the query designer.

Multi-value Lookup and Projected Fields

Starting from SharePoint 2010, it is possible to select additional fields in a lookup target list (a projection). Amongst other things, you will be able to display (through views) those fields as if they were part of your list.

Lookup Fields projection.

When expanding a multi-value lookup column (see the screen shot below) – meaning breaking down multiple values into single value by duplicating each item as if you were doing a join between the item and the lookup values - , Enesys RS Data Extension 3.8 and earlier will just duplicate projected fields value like with any other fields instead of retrieving the value that matches the single lookup value.

Expland multi-values column.

Enesys RS Data Extension 3.9, provides support for projected fields and will automatically extract the single value that matches the lookup value item.

Projected Fields are properly expanded in Enesys RS Data Extension 3.9.

Send Technical Data and Error Log the Easy Way

Because Enesys RS Data Extension supports Reporting Services 2005, 2008, 2008R2 and 2012 as well as SharePoint 2007, 2010 and 2013, it’s always tricky for the support team to get the necessary customer configuration information without trying to guess or exchanging several emails.

In order to make things much easier in that area, Enesys RS Client Configuration and Enesys RS Server Configuration tools now offer an option to prepare technical data and error log information in a zip file that can be sent to our support.

Enesys RS Client Configuration - Save Debug Info.

When clicking on Save Debug Info button you will be proposed to specify the name of a zip file that will contain various files that will provide our support valuable information for providing assistance (error log and configuration data).

 

Release History

Click on a version to display features and fixes for this specific version.

  • Enesys RS Data Extension 3.8.125
  • Enesys RS Data Extension 3.8.125

      Fix:

    • Corrected an issue recurring events - in some specific cases, Yearly By Day exceptions would not be handled correctly.
  • Enesys RS Data Extension 3.8.114
  • Enesys RS Data Extension 3.8.114

     Fix:

    • Corrected an issue introduced in v3.8 with the EnableObjectModel default value, which could result in an exception: System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
    • Corrected an issue introduced in v3.8 with the use of the Object Model on a SharePoint 2010 server using Forms authentication.

     

  • Enesys RS Data Extension 3.8.111
  • Enesys RS Data Extension 3.8.111

    Fixes:

    • Fixed a bug that would cause random report failures. When looking at the logfile "ERSDE2008Error.log", you should see the following error: "Collection was modified; enumeration operation may not execute."
  • Enesys RS Data Extension 3.8.103
  • Enesys RS Data Extension 3.8.103

    New Features

    Simpler Approach for Distinct Field Values

    Retrieveing distinct field values is extremely useful when using report parameters. With Enesys RS Data Extension version 3.7 and earlier, you could use an additional "SqlQuery" statement to get distinct values from a SharePoint list.

    Because this approach is so common, Enesys RS Data Extension 3.8 makes it possible to get distinct values from a list without having to use an additional SqlQuery statement. You can specify that you want distinct values directly within the “List” properties as shown in the following screen shot:

    You can specify that you want distinct field values at the list level.

    Retrieving Choice Values from a Choice Column

    When using a report parameter to filter a list based on the values  of a choice column (ie: status, priority,…), you may want to consider two approaches:

    1. You will only display values that are already in use. Say you are filtering issues based on a specific “Priority” that the user can select when running the report. Even though the “Priority” is a SharePoint choice column that contains the following 3 values (High, Normal and low), if you don’t have any issues with a “low” priority value, you may not want to display “Low” as a possible choice for filtering out issues.
      With that approach, you consider that it is not necessary to bother the user with some value that does not return any items.
    2. You will display all possible values regardless of its selection will return any values. If we take the previous example, you want to display “low” as a possible choice for filtering issues even if you don’t have any issues with low priority.
      With that approach, you are considering that displaying all the possible values and not returning any items for a specific value brings some meaningful information to the user.

    Both approaches are perfectly legitimate. It all depend on the business case.

    In version 3.7 and earlier of Enesys RS Data Extension, only the first scenario can be implemented. To implement this approach, you will select distinct values from the specific field you want to filter and use them for the report parameter values.

    Enesys RS Data Extension 3.8 offers the possibility to retrieve the choice values from a SharePoint choice columns. With this new feature, you can therefore implement the second scenario described earlier and present all the possible values for the column you are filtering as part of a report parameter.

    Retrieving choices from a column of type "Choice”

    Enesys RS Data Extension 3.8 provides a new statement for retrieving “choices” from list or site columns of type choice.

    When adding “Column Choices” statement to your query, you are proposed to either retrieve choices from a specific list column or from a column defined at the site level:

    Adding Column Choices statement.

    When selecting the option, “Retrieve choices from a list column”, you get the usual dialog box where you can select the desired list:

    When selecting the option, “Retrieve choices from a list column”, you get the usual dialog box where you can select the desired list.

    When selecting a list or a site, you will only be proposed the choice columns available in the list or the site. As part of the statement, you can only select a single column to retrieve choices values from (it would not make many sense to return value from multiple choices columns in a single result set). Executing the statement will return choices associated with the column.

    Selecting Choice Column.

    SQL Server Reporting Services 2012 compatibility

    SQL Server Reporting Services 2012 brings quite a few changes:

    • Business Intelligence Development Studio (BIDS) is now called SQL Server Data Tools (SSDT) and runs under visual studio 2010 shell. It doesn’t mean you need visual studio. The visual studio 2010 core interface will be automatically installed when installing SSDT.
    • SharePoint integration in now implemented as a SharePoint 2010 Shared Service.

    Enesys RS Data Extension 3.8 addresses the various configuration changes to work with Reporting Services 2012.

    When installed in SharePoint Integration mode, The “Enesys RS Server Configuration” tool reflects the new “SharePoint Service Application” as shown in the following screen-shot:

    SSRS as a SharePoint Service Application within Enesys RS Server Configuration.

    Enesys RS Client Configuration” tool reflects the new Microsoft terminology when Enesys RS Data Extension is installed along SQL Server Data Tools:

    SQL Server Data Tool.

    Within SSDT 2012 (Visual Studio 2010 shell), you get the familiar tools for building reports and sophisticated queries:

    Building reports with SQL Server Data Tools 2012.

    Merging Multiple Lists

    Enesys RS Data Extension 3.8 provides additional flexibility and power for merging multiple lists with the new “ListsMerge” statement.

    The new “ListsMerge” statement lets you merge a set of lists specified by another statement. You will configure “ListsMerge” statement so that the lists to be merged are specified in another statement which means that you can store the lists in whatever way you want as long as you can use one of the statement provided by Enesys RS Data Extension to retrieve them.

    For instance, you may want to use a SharePoint list to maintain the lists/libraries that you would like to merge. Using this approach, adding or removing a list from your report is just a matter of adding or deleting an item in your SharePoint list without having to change your report.

    In order to merge a set of lists, you need to specify a statement that returns a set of lists. You will also need to specify an existing list as a reference so that the schema can be inferred at design time to let you choose the necessary fields and apply the desired filters:

    Merging a set of Lists with the ListsMerge statement.

    The source statement needs to have two columns that provides list name and site URL. The designer will ensure those columns are available before you can create the statement:

    Merging a set of Lists - source statement validation.

    Two additional columns are provided to let you know to which site and list belongs an item. This can be useful for grouping the resulting data:

    Merging a set of Lists - source site and list.

    Here is an example SharePoint list that can be used as a source for merging multiple lists from multiple sites. Once your report is built upon this list for merging data, you don't need to change your report to add or remove a list:

    Merging a set of Lists - sample SharePoint list that can be used as a source for merging a set of lists.

    Additional Information:

    Visual Query Designer Improvements

    As with most releases, Enesys RS Data Extension 3.8 brings various user interface improvements to make your life easier when designing queries.

    Filtering using parameters

    In many cases you will want to use report parameters when filtering SharePoint lists data. Until now, it was necessary to use a very specific syntax (the name of a parameter surrounded by @ and !), to indicate that you are referring to a report parameter.

    That’s not really difficult but not always intuitive especially when discovering the product.

    Therefore, with Enesys RS Data Extension 3.8, a "Parameter…" option is available as shown in the following screen shot:

    Filtering using parameters.

    When selecting the “Parameter…” option, a dialog box lets you either select an existing parameter or enter a new parameter name:

    Selecting or creating a parameter.

    Filtering on choice columns

    When filtering on SharePoint columns of type Choice, choices values are displayed and available for selection as shown in the following screen shot:

    Filtering on Choice Columns.

    This is also available for some specific columns like the workflow status:

    Filtering on Workflow status.

    Note that the workflow status value is of type integer. The label displayed next to the integer value is for visual help only.

    Renaming Statements

    In previous versions of Enesys RS Data Extension, renaming a statement could lead to an overall invalid query when the statement was used, for instance, in a SqlQuery statement for joining multiple lists. Indeed, in that case, the SQL Select statement is not updated to reflect the new name of the statement.

    If you look at the screen shot below, the query includes a “SqlQuery” statement that joins both “Issues1” and “Issues” statements. With versions prior to 3.8, renaming “Issues1” will not update the “SELECT” clause. It will be necessary to make the modification manually.

    With Enesys RS Data Extension 3.8, renaming a statement will automatically update the overall query to reflect the change. No more manual update is necessary.

    Renaming statements.

    Statement Fields

    Enesys RS Data Extension offers various specialized Statements for retrieving data from SharePoint lists, InfoPath libraries, SQL Server, Oracle, and much more.

    You can mix and match the data in those statements by using a “SqlQuery” statement that lets you use SQL Select syntax.

    At time, when creating sophisticated queries, things can get complex. Intellisense features made available a few versions ago were a great step in the right direction. In version 3.7, we added visual information by displaying - in the query statements panel (the yellow area in the image below) - the fields associated with a specific statement. This was however limited to a few set of statements.

    With Enesys RS Data Extension 3.8 we have generalized this approach to all statements. You can therefore have an overall view of your statements and fields which greatly helps when building complex queries:

    Statement fields displayed in the statement panel.

    Improved XmlQuery Statement

    The XmlQuery statement lets you retrieve and manipulate XML data from an URL you specify. With previous versions of Enesys RS Data Extension, you were bound to use an XPath expression to specify the data you wanted to retrieve from your XML data. Though this may be satisfying in many cases, you may need to retrieve data from a more complex XML structure that would not translate using a single XPath expression.

    Capitalizing upon the recent developments on the InfoPath statement, the XmlQuery statement now offers a similar approach for selecting data (ElementPath) in addition to the XPath expression that is still supported.

    When creating a new XmlQuery statement, both options are proposed as shown in the following screen shot:

    Support for XPath and ElementPath queries.

    ElementPath approach

    When using the new ElementPath approach, you will be able to specify the data you need with more precision than using the XPath approach.

    Moreover you get you get the same designer control that is available with InfoPath statement:

    XML ElementPath Query Designer.

    XPath approach

    The XPath approach is the only available method with version 3.7 and earlier. It lets you write an XPath expression to specify the data you would like to retrieve from your XML data. Though it has some limitations when you want to deal with retrieving data at various level of your XML hierarchy, it can also be quite helpful when you want to retrieve nodes whatever their position in your XML schema.

    Enesys RS Data Extension 3.8 brings two improvements to the XPath approach.

    XML Schema viewer

    You can view the XML schema while writing your XPath expression:

    XML Schema is displayed as an helper for building XPath expression.

    Field Selection

    When using an XPath expression, you don’t have much control on the elements/attributes returned by the expression. Say you use an expression like “//Item”, you would end up having all the child element of “Item” being converted to fields in your query.

    You can now select the fields to include:

    Select Specific fields to further refine your Xpath query expression.

    Run Queries up to 50 times faster with Statement Filtering

    Th new statement filtering feature let's you filter a SharePoint list using data from another statement, be it another SharePoint list or any other statement that gets date from SQL Server, Oracle...

    When joining multiple SharePoint lists using an Enesys RS Data Extension SqlQuery statement, the "join" operation takes place after lists items are retrieved. Therefore you may retrieve from your SharePoint server unecessary items that will be discarderd once doing the "join" operation. Statement Filtering will allow you to use the resulting data of another statement in order to filter at the SharePoint list level (as opposed to filtering once the data is retrieved). This approach can make a huge difference in scenarios where you are manipulating large lists and your join operations will only return a few items.

    This feature is better explained by using a concrete sample. Please read the following article for a detailed scenario that explains why and how to use this feature.

    Other Improvements

    •  Client and Server Configuration tool now adds links to Log folder for easier access.
    •  Server Configuration tool now supports specifying a default value for the enableObjectModel data source property.
    • The Server Configuration tool doesn’t reset IIS when Enesys RS Data Extension is configured on Reporting Services 2005. A restart of the Report Server service is done instead.
    •  Improved "In" performances when using SharePoint 2010 by converting the pseudo-CAML element into the new SharePoint 2010 "In" CAML element.
    • A new IncludesAll pseudo-CAML element allows filtering a multi-values column to ensure that returned items contain all the given values.

    Fixes

    • Corrected a bug with the render of specific characters when used in Note fields.
  • Enesys RS Data Extension 3.7.33
  • Enesys RS Data Extension 3.7.33

    Fix:

    • Corrected a bug when designing infoPath statements. In some cases, the designer was looking for the XSN file at a wrong place.
    • Corrected a bug with infoPath statements that prevented setting the useDisplayName attribute to true.

     

  • Enesys RS Data Extension 3.7.27
  • Enesys RS Data Extension 3.7.27

    Fix:

    • Corrected a bug within the infoPath statement that prevented to execute the statement on an InfoPath form that referenced several schemas.
      For example, when using the people picker control, you would have an error similar to "The http://schemas.microsoft.com/office/infopath/2007/PartnerControls:Person element is not declared".
    • Corrected a bug with SharePoint 2007 and Reporting Services 2005 when Reporting Services is configured in SharePoint Integrated mode.
  • Enesys RS Data Extension 3.7.20
  • Enesys RS Data Extension 3.7.20

    Fixed:

    • A bug with SharePoint 2007 and Reporting Services 2005 in SharePoint Integrated mode which prevented the use of the Object Model.
    • A bug which prevented to use the Object Model when doing aSiteCollection queries and one of the sites contained special characters.
    • A bug within the query designer which prevented the creation of aSiteContentTypes statements inside the new statement toolbar.

     

  • Enesys RS Data Extension 3.7.19
  • Enesys RS Data Extension 3.7.19

    New InfoPath features

    Enesys RS Data Extension offers a brand new statement dedicated to InfoPath forms.

    This statement lets you retrieve data from both InfoPath promoted and non-promoted fields:

    Enesys RS Data Extension returns the data using the data type specified in the InfoPath form. However, you can easily select a different data type:

    Using Integrated Security with Forms and Claims authentication

    When used with Reporting Services 2008R2 in SharePoint Integrated Mode, Enesys RS Data Extension 3.7 provides a second data extension (server side) that lets you use the SharePoint Token of the connected user instead of relying on passing Windows identity credentials.

    This new extension ("Enesys RS Token Data Extension") allows you to use "Integrated Security or SharePoint token" with Windows or Forms authentication and Claims based web applications, without the need to use Kerberos.

    Item Versions Performance Boost

    If you have used Enesys RS Data Extension for building reports that deal with item version, you certainly know that this is a time consuming process. The main reason is the limitation of the SharePoint Web Services API in that specific area.

    By using the Object Model, Enesys RS Data Extension v3.7 now provides dramatically improved performances when retrieving item versions in SharePoint integrated mode.

    The following table provides performance comparisons between the version 3.6 and the version 3.7. Those results are based on a query that retrieves 500 items from a list, each item having 4 versions:

      Version 3.6 Version 3.7
    SharePoint Integrated Mode
    Ratio
    500 items
    Retrieving version from 9 fields
    03:10 00:18 10x
    500 items
    Retrieving version from 1 field
    00:38 00:07 5x

    Reference List for RollUpLists statements

    In previous versions of Enesys RS Data Extension, the SharePoint list used to build the target query schema was the first list available. In case all the lists you are aggregating are strictly identical, this is not an issue. But in case some of your lists have additional fields that you would like to be part of the target dataset, you will have to ensure that the first list (which is used to build the schema) has all the necessary fields. Depending on your scenario, this may not be practical to achieve.

    Enesys RS Data Extension 3.7 now allows you to specify a referenceSite attribute that will contain the URL to the site containing the list used to build the schema. Similarly to the relativeSiteUrl, the referenceSite is a URL relative to the data source URL.

    Query Designer Improvements

    Enesys RS Data Extension 3.7 brings various user interface improvements.

    Intellisense

    • Parameters for functions that have the same name as keywords (for example the REPLACE function is also a keyword) are now properly displayed.
    • In order to simplify field selection, Intellisense for SQLite function is now disabled by default. You can re-enable it by clicking on the appropriate button:
    • Corrected a bug which prevented Intellisense for some statements when joining 3 or more statements with "JOIN tableName ON condition".

    New Query Statements toolbar

    A new toolbar was added into the Query Statements panel to allow you to quickly manipulate the statements.

    This toolbar allows you to:

    • Add new statements
    • Go to the Properties form of the selected statement
    • Delete the selected statement
    • Move up/down the selected statement inside the statement list

    New Form for adding statements

    By clicking on the "New" menu item, a form is displayed that lists all the available statements, grouped by category:

    Removed the Columns/Filtering/Sorting tab

    For simplification, the Columns/Filtering/Sorting tab was removed and all its functionalities where moved in order to be available in the main design area.

    The "Query columns" panel was removed.

    You can now reorder the fields inside the Query Statements panel (along with the possibility to delete them):

    The "Columns sorting order" panel was moved into a new "Order By" tab of the Columns tab:

    All the previous functionalities of the control are kept, and this new control offers an enhanced field selector:

    The "Query conditions" tab was moved into the new "Filters" tab of the Columns tab:

    All the previous functionalities of the Query conditions panel were preserved, and some new features were added:

    New advanced filtering control

    Support for moving conditions/groups (up/down and left/right):

    Support for adding parent groups to a specific group:

    Improved field selector by using an autocomplete drop down list:


    Changing the operator no longer changes the value:


    Better support for LookupId and IncludeTimeValue options:


    Showing/Hiding panels

    By default, the Results panel is now hidden. But you can quickly show it by clicking on the appropriate button:

    Similarly, you can quickly show/hide the statement panel by clicking on the appropriate button:

    Other improvements

    • Added two new SQLite collating sequences: UTF8 and UTF8CI. They bring support for UTF-8 comparisons when sorting/grouping data. The UTF8 collating function is case sensitive while the UTF8CI one is case insensitive.

      Usage:
      SELECT foo FROM bar ORDER BY foo COLLATE UTF8
      or
      SELECT foo FROM bar GROUP BY foo COLLATE UTF8CI

      This is useful when sorting/grouping data that has diacritics or non-Latin characters.
    • Corrected a bug which prevented to roll up data starting from a site having spaces in its URL.
  • Enesys RS Data Extension 3.6.31
  • Enesys RS Data Extension 3.6.31

    Fix:

    • Fixed a bug that prevented to query a List which contained some fields with invalid properties.
    • Fixed a bug which prevented to roll up data starting from a site which contained spaces in its URL.
    • Fixed a bug which prevented the use of multivalues parameter inside the sqlData's IN clause in some cases.

     

  • Enesys RS Data Extension 3.6.28
  • Enesys RS Data Extension 3.6.28

    New:

    • XmlQuery statement User Interface has been updated to simplify the usage of report parameters for specifying a URL.

    Fix:

    • The characters accepted inside the name of parameters are now checked for valid values (unicode letters, digits, _, - and #). This allows having a @ character inside the connection string of the sqlData statement.
    • Removed the possibility to sort the columns inside the Columns panel. This option was not only useless (considering dynamic search is available) but also confusing as there was no way of reverting to natural order.

     

  • Enesys RS Data Extension 3.6.26
  • Enesys RS Data Extension 3.6.26

    New:

    • Added support for XML namespaces to the xmlQuery statement. It's now possible to specify a namespace when filtering the XML data through the ElementPath property (ie: //my:element).

    Fix:

    • Corrected a bug inside the Query Designer introduced inside the v3.6.23 that didn't allow you to load a query with IsNull or IsNotNull conditions on Lookup and DateTime columns. Note that it was still possible to edit the query in XML mode and that the bug did not affect the proper execution of a query using such a condition.

     

  • Enesys RS Data Extension 3.6.23
  • Enesys RS Data Extension 3.6.23

    Reporting from Survey lists

    Enesys RS Data Extension offers a new statement that lets you retrieve Survey lists data in a format that makes it possible to build reports. We are also offering a ready-made generic report that can be used with any Survey list.

    Querying Oracle databases

    Starting from the version 3.4, the sqlServerQuery statement allowed you to retrieve data from any SQL Server database. In this new version of Enesys RS Data Extension, the sqlServerQuery statement is renamed to sqlData and is extended by adding support for Oracle databases.

    The behavior is similar, you just have to select between SQL Server and Oracle when you create the statement:

    Then, enter the connection string properties:

    You can now query the database:

    Query Designer - Major Intellisense improvements

    SqlQuery statement is central to Enesys RS Data Extension innovative approach to build sophisticated queries. In this version, we have made several improvements regarding the Intellisense.

    Extended Statement Support

    With the previous versions, only the statement name was provided for sqlData, xmlQuery and sqlQuery statements, you still had to write the field names without any support from intellisense.

    In this version, Intellisense is now provided for fields resulting from any statement:

    • For example, a database queried using the sqlData statement:
    • Or a RSS feed queried using the xmlQuery statement:
    • After having joined SQL Server and SharePoint data using a sqlQuery statement, you can use Intellisense inside a second sqlQuery statement:

    SQL Functions support

    SQLite functions are listed along with their associated parameters and a brief description:

    Parameter description is available when editing a function:

    Better Contextual Support

    Real-time query parsing has been much improved in order to provide contextual  Intellisense support:

    • No statement is selected, the fields are not available:
    • Only the Products statement is selected, only its fields are available:
    • Both statements are joined, all the fields are available:
    • Support for table aliases:

      The "p" name is detected as an alias of the "Products" table; therefore, fields from the Products table are available.

      "pc" is recognized as an alias of the "Product categories" table, its fields are available.

    SELECT and JOIN Snippets

    Two "code snippets" were added for quickly adding SQL clauses:

    • A "SELECT" snippet for inserting a SELECT clause with a FROM clause that selects a single statement:

      By validating (with the Tab key), the snippet is inserted:

      Available statements are proposed for selection:

      Enter/select the desired statement and click on Enter to validate the snippet modification. The caret is then moved just after the SELECT so that you can select your fields:
    • A "JOIN" snippet for inserting a JOIN clause:

      By clicking on the TAB key, you insert the snippet:

      Three placeholders are available for specifying the joined table name and the two columns used as part of the join:

    Using parameters and variables for specifying the URL and the title

    The Properties form of list, survey, mergeLists and rollUpLists statements now has a "Url and Title" tab that allows you to easily change the way you specify the list title and its relative site URL:

    When specifying a parameter, the value is specified into the "DefaultParameterValues" query option:

    The query now has an options statement with the value specified:

    When Reporting Services will retrieve the list schema, it will use this default value, so that you don’t get prompted for specifying the parameter values each time you edit the query.

    Query Designer – User Interface Improvements

    The version 3.6 includes some improvements regarding the User Interface that will enhance your query design experience.

    Adding a list statement

    The dialog box for selecting a list has been completely revamped as shown in the following screenshot:

    Key improvements:

    • Using a data source variable for specifying the relative site URL
    • Filtering lists by name, type and visibility

    Adding a rollUpLists statement

    Similarly to the "Add list statement" dialog box, the "Add rollUpLists statement" dialog box was revamped:

    Key improvements:

    • Improved performances by limiting the data retrieved from SharePoint
    • "On-demand" retrieval of the sub-sites lists
    • Using a data source variable for specifying the relative site URL
    • Filtering lists by name, type and visibility

    Selecting columns

    SharePoint lists may have numerous columns and it may not be easy to go through every column to look for a specific column. We have added some options to the “Columns” tab, as you can see on the following screenshot:

    Key improvements:

    • Dynamic filter of the columns based on their internal and display name.
    • Show/hide the hidden columns with a single click
    • Select/unselect all displayed columns with a single click

    Other improvements

    • The aListPermissions and aSitePermissions statements now use the correct enumeration for the permissions.
    • Improved Null parameter value handling within CAML queries:
      • Eq operator is transformed to IsNull if the parameter value is null.
      • Neq operator is transformed to IsNotNull if the parameter value is null.
    • Null parameter values are properly handled inside sqlData (previously named sqlServerQuery) statements.
    • Parameters may now be used inside the title attribute of the list, mergeLists and rollUpLists statements. This allows you to dynamically change the selected list at report-time, granted that lists have the same selected fields.
    • Corrected a bug with SharePoint 2010 that caused an error to be thrown when retrieving Item Versions for the Editor column.

     

  • Enesys RS Data Extension 3.5.27
  • Enesys RS Data Extension 3.5.27

    Fix:

    • Corrected a bug that would result in an exception when using the stripHtml feature.This is a regression bug introduced in version 3.5.
    • Corrected a bug with itemVersions and SharePoint 2010: when the Editor column was selected inside the itemVersionFields, an error would be thrown.
  • Enesys RS Data Extension 3.5.26
  • Enesys RS Data Extension 3.5.26

    Fix:

    • Corrected a bug with Forms Based Authentication which failed to properly detect the license type in some specific cases, resulting in the inability to query a SharePoint server configured with FBA.
    • Corrected the Object Model detection, which wrongly detected the Object Model in some cases.
    • Corrected a problem that would prevent modifying the objectModelMethod attribute in the rollUpLists statements.
    • Corrected a bug in the Query Designer which caused the toolbar not to be shown when using BIDS 2008 R2 with French language.
  • Enesys RS Data Extension 3.5.22
  • Enesys RS Data Extension 3.5.22

    Changed:

    • Removed the use of temporary files that could conflict with the permissions of the Reporting Services Execution account. This could lead to a "Unable to open database file" error in specific cases.
  • Enesys RS Data Extension 3.5.19
  • Enesys RS Data Extension 3.5.19

    New:

    • Using Object Model for rolling up data:
      In this version, Enesys RS Data Extension can take advantage of the SharePoint object model when Reporting Services is installed in SharePoint Integrated mode (or in Standalone mode when your report server is installed on a Web Front End).
      This can lead to tremendous performance improvement in some scenarios.
       
    • Support for Forms Based Authentication:
      Enesys RS Data Extension is now able to query a SharePoint server using Forms Based Authentication by simply setting the “authenticationMode” Connection String option to “Forms”. This feature is only available in Standard and Enterprise Editions.
       
    • Specifying fields for which to retrieve item versions:
      In previous versions, retrieving item versions was an all or nothing option. Enesys RS Data Extension would retrieve version information for all the selected fields.
      Retrieving item versions being a time consuming process, in this version, we added the possibility to specify the fields for which you need version information.

       
    • Using Data Source variables inside the SqlServerQuery’s connection string:
      In this version, you can now specify “data source variables” inside the sqlServerQuery statement’s Connection String.
      This additional feature makes it easier for moving reports from a development environment to a production environment by simply modifying the shared data source.
       
    • Advanced Properties Form:
      We have added a new “Properties” form that you can access by right clicking on a statement or by clicking on the appropriate button inside the Properties tab:
        

      This new “Properties” form is available for all the statements and offers a better user experience for editing the most common statement properties.


      It automatically validates the data, and displays a small icon with information about the error if the data is invalid:

       
    • New Data Source Connection String options:
      Three new data source connection string options are available to help you fine tune how Enesys Data Extension retrieves data from your SharePoint server:
      • timeout: The time (in milliseconds) to wait for each Web Services call to execute before a timeout occurs. Default value is 300000 (5 minutes).
      • retryTime: The time (in milliseconds) to wait before retrying a call when a timeout occurs. If the value is specified, a single retry will be made, if the value is not specified, no retry will be made.
      • sleepTime: The time (in milliseconds) to wait between two calls made to retrieve the list items (a paging mechanism is used to get items from lists that contain more than 2000 items). If no value is specified, the next call will be made just after the first one is parsed.
       

    Bug corrections:

    • Corrected a bug with itemVersions and Document Library
    • Corrected a bug that prevented the use of a quote character inside the tableName attribute when using the rollUpLists statement.
    • Corrected a bug inside the Query Designer that displayed Intellisense for invalid lookup ID column.
    • Corrected a bug inside the "Add List Statement" form that could lead to an error when trying to add a list.

    For more information about the new features, see the documentation.

  • Enesys RS Data Extension 3.4.7
  • 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
  • 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
  • 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
  • Enesys RS Data Extension 3.4.4

    Fix:

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

  • Enesys RS Data Extension 3.4.3
  • 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.

      image

       

      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:

      image

       

      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:

      image

       

      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:

      image


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

    Value Description
    Default Returns only the files and subfolders of a specific folder. 
    FilesOnly Returns only the files of a specific folder. 
    Recursive Returns all files of all folders starting from the specified folder. 
    RecursiveAll

    Returns all files and all subfolders of all folders starting from the specified folder. 

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

Release History

Click on a version to display features and fixes for this specific version.

  • Enesys RS Data Extension 3.8.125
  • Enesys RS Data Extension 3.8.125

      Fix:

    • Corrected an issue recurring events - in some specific cases, Yearly By Day exceptions would not be handled correctly.
  • Enesys RS Data Extension 3.8.114
  • Enesys RS Data Extension 3.8.114

     Fix:

    • Corrected an issue introduced in v3.8 with the EnableObjectModel default value, which could result in an exception: System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
    • Corrected an issue introduced in v3.8 with the use of the Object Model on a SharePoint 2010 server using Forms authentication.

     

  • Enesys RS Data Extension 3.8.111
  • Enesys RS Data Extension 3.8.111

    Fixes:

    • Fixed a bug that would cause random report failures. When looking at the logfile "ERSDE2008Error.log", you should see the following error: "Collection was modified; enumeration operation may not execute."
  • Enesys RS Data Extension 3.8.103
  • Enesys RS Data Extension 3.8.103

    New Features

    Simpler Approach for Distinct Field Values

    Retrieveing distinct field values is extremely useful when using report parameters. With Enesys RS Data Extension version 3.7 and earlier, you could use an additional "SqlQuery" statement to get distinct values from a SharePoint list.

    Because this approach is so common, Enesys RS Data Extension 3.8 makes it possible to get distinct values from a list without having to use an additional SqlQuery statement. You can specify that you want distinct values directly within the “List” properties as shown in the following screen shot:

    You can specify that you want distinct field values at the list level.

    Retrieving Choice Values from a Choice Column

    When using a report parameter to filter a list based on the values  of a choice column (ie: status, priority,…), you may want to consider two approaches:

    1. You will only display values that are already in use. Say you are filtering issues based on a specific “Priority” that the user can select when running the report. Even though the “Priority” is a SharePoint choice column that contains the following 3 values (High, Normal and low), if you don’t have any issues with a “low” priority value, you may not want to display “Low” as a possible choice for filtering out issues.
      With that approach, you consider that it is not necessary to bother the user with some value that does not return any items.
    2. You will display all possible values regardless of its selection will return any values. If we take the previous example, you want to display “low” as a possible choice for filtering issues even if you don’t have any issues with low priority.
      With that approach, you are considering that displaying all the possible values and not returning any items for a specific value brings some meaningful information to the user.

    Both approaches are perfectly legitimate. It all depend on the business case.

    In version 3.7 and earlier of Enesys RS Data Extension, only the first scenario can be implemented. To implement this approach, you will select distinct values from the specific field you want to filter and use them for the report parameter values.

    Enesys RS Data Extension 3.8 offers the possibility to retrieve the choice values from a SharePoint choice columns. With this new feature, you can therefore implement the second scenario described earlier and present all the possible values for the column you are filtering as part of a report parameter.

    Retrieving choices from a column of type "Choice”

    Enesys RS Data Extension 3.8 provides a new statement for retrieving “choices” from list or site columns of type choice.

    When adding “Column Choices” statement to your query, you are proposed to either retrieve choices from a specific list column or from a column defined at the site level:

    Adding Column Choices statement.

    When selecting the option, “Retrieve choices from a list column”, you get the usual dialog box where you can select the desired list:

    When selecting the option, “Retrieve choices from a list column”, you get the usual dialog box where you can select the desired list.

    When selecting a list or a site, you will only be proposed the choice columns available in the list or the site. As part of the statement, you can only select a single column to retrieve choices values from (it would not make many sense to return value from multiple choices columns in a single result set). Executing the statement will return choices associated with the column.

    Selecting Choice Column.

    SQL Server Reporting Services 2012 compatibility

    SQL Server Reporting Services 2012 brings quite a few changes:

    • Business Intelligence Development Studio (BIDS) is now called SQL Server Data Tools (SSDT) and runs under visual studio 2010 shell. It doesn’t mean you need visual studio. The visual studio 2010 core interface will be automatically installed when installing SSDT.
    • SharePoint integration in now implemented as a SharePoint 2010 Shared Service.

    Enesys RS Data Extension 3.8 addresses the various configuration changes to work with Reporting Services 2012.

    When installed in SharePoint Integration mode, The “Enesys RS Server Configuration” tool reflects the new “SharePoint Service Application” as shown in the following screen-shot:

    SSRS as a SharePoint Service Application within Enesys RS Server Configuration.

    Enesys RS Client Configuration” tool reflects the new Microsoft terminology when Enesys RS Data Extension is installed along SQL Server Data Tools:

    SQL Server Data Tool.

    Within SSDT 2012 (Visual Studio 2010 shell), you get the familiar tools for building reports and sophisticated queries:

    Building reports with SQL Server Data Tools 2012.

    Merging Multiple Lists

    Enesys RS Data Extension 3.8 provides additional flexibility and power for merging multiple lists with the new “ListsMerge” statement.

    The new “ListsMerge” statement lets you merge a set of lists specified by another statement. You will configure “ListsMerge” statement so that the lists to be merged are specified in another statement which means that you can store the lists in whatever way you want as long as you can use one of the statement provided by Enesys RS Data Extension to retrieve them.

    For instance, you may want to use a SharePoint list to maintain the lists/libraries that you would like to merge. Using this approach, adding or removing a list from your report is just a matter of adding or deleting an item in your SharePoint list without having to change your report.

    In order to merge a set of lists, you need to specify a statement that returns a set of lists. You will also need to specify an existing list as a reference so that the schema can be inferred at design time to let you choose the necessary fields and apply the desired filters:

    Merging a set of Lists with the ListsMerge statement.

    The source statement needs to have two columns that provides list name and site URL. The designer will ensure those columns are available before you can create the statement:

    Merging a set of Lists - source statement validation.

    Two additional columns are provided to let you know to which site and list belongs an item. This can be useful for grouping the resulting data:

    Merging a set of Lists - source site and list.

    Here is an example SharePoint list that can be used as a source for merging multiple lists from multiple sites. Once your report is built upon this list for merging data, you don't need to change your report to add or remove a list:

    Merging a set of Lists - sample SharePoint list that can be used as a source for merging a set of lists.

    Additional Information:

    Visual Query Designer Improvements

    As with most releases, Enesys RS Data Extension 3.8 brings various user interface improvements to make your life easier when designing queries.

    Filtering using parameters

    In many cases you will want to use report parameters when filtering SharePoint lists data. Until now, it was necessary to use a very specific syntax (the name of a parameter surrounded by @ and !), to indicate that you are referring to a report parameter.

    That’s not really difficult but not always intuitive especially when discovering the product.

    Therefore, with Enesys RS Data Extension 3.8, a "Parameter…" option is available as shown in the following screen shot:

    Filtering using parameters.

    When selecting the “Parameter…” option, a dialog box lets you either select an existing parameter or enter a new parameter name:

    Selecting or creating a parameter.

    Filtering on choice columns

    When filtering on SharePoint columns of type Choice, choices values are displayed and available for selection as shown in the following screen shot:

    Filtering on Choice Columns.

    This is also available for some specific columns like the workflow status:

    Filtering on Workflow status.

    Note that the workflow status value is of type integer. The label displayed next to the integer value is for visual help only.

    Renaming Statements

    In previous versions of Enesys RS Data Extension, renaming a statement could lead to an overall invalid query when the statement was used, for instance, in a SqlQuery statement for joining multiple lists. Indeed, in that case, the SQL Select statement is not updated to reflect the new name of the statement.

    If you look at the screen shot below, the query includes a “SqlQuery” statement that joins both “Issues1” and “Issues” statements. With versions prior to 3.8, renaming “Issues1” will not update the “SELECT” clause. It will be necessary to make the modification manually.

    With Enesys RS Data Extension 3.8, renaming a statement will automatically update the overall query to reflect the change. No more manual update is necessary.

    Renaming statements.

    Statement Fields

    Enesys RS Data Extension offers various specialized Statements for retrieving data from SharePoint lists, InfoPath libraries, SQL Server, Oracle, and much more.

    You can mix and match the data in those statements by using a “SqlQuery” statement that lets you use SQL Select syntax.

    At time, when creating sophisticated queries, things can get complex. Intellisense features made available a few versions ago were a great step in the right direction. In version 3.7, we added visual information by displaying - in the query statements panel (the yellow area in the image below) - the fields associated with a specific statement. This was however limited to a few set of statements.

    With Enesys RS Data Extension 3.8 we have generalized this approach to all statements. You can therefore have an overall view of your statements and fields which greatly helps when building complex queries:

    Statement fields displayed in the statement panel.

    Improved XmlQuery Statement

    The XmlQuery statement lets you retrieve and manipulate XML data from an URL you specify. With previous versions of Enesys RS Data Extension, you were bound to use an XPath expression to specify the data you wanted to retrieve from your XML data. Though this may be satisfying in many cases, you may need to retrieve data from a more complex XML structure that would not translate using a single XPath expression.

    Capitalizing upon the recent developments on the InfoPath statement, the XmlQuery statement now offers a similar approach for selecting data (ElementPath) in addition to the XPath expression that is still supported.

    When creating a new XmlQuery statement, both options are proposed as shown in the following screen shot:

    Support for XPath and ElementPath queries.

    ElementPath approach

    When using the new ElementPath approach, you will be able to specify the data you need with more precision than using the XPath approach.

    Moreover you get you get the same designer control that is available with InfoPath statement:

    XML ElementPath Query Designer.

    XPath approach

    The XPath approach is the only available method with version 3.7 and earlier. It lets you write an XPath expression to specify the data you would like to retrieve from your XML data. Though it has some limitations when you want to deal with retrieving data at various level of your XML hierarchy, it can also be quite helpful when you want to retrieve nodes whatever their position in your XML schema.

    Enesys RS Data Extension 3.8 brings two improvements to the XPath approach.

    XML Schema viewer

    You can view the XML schema while writing your XPath expression:

    XML Schema is displayed as an helper for building XPath expression.

    Field Selection

    When using an XPath expression, you don’t have much control on the elements/attributes returned by the expression. Say you use an expression like “//Item”, you would end up having all the child element of “Item” being converted to fields in your query.

    You can now select the fields to include:

    Select Specific fields to further refine your Xpath query expression.

    Run Queries up to 50 times faster with Statement Filtering

    Th new statement filtering feature let's you filter a SharePoint list using data from another statement, be it another SharePoint list or any other statement that gets date from SQL Server, Oracle...

    When joining multiple SharePoint lists using an Enesys RS Data Extension SqlQuery statement, the "join" operation takes place after lists items are retrieved. Therefore you may retrieve from your SharePoint server unecessary items that will be discarderd once doing the "join" operation. Statement Filtering will allow you to use the resulting data of another statement in order to filter at the SharePoint list level (as opposed to filtering once the data is retrieved). This approach can make a huge difference in scenarios where you are manipulating large lists and your join operations will only return a few items.

    This feature is better explained by using a concrete sample. Please read the following article for a detailed scenario that explains why and how to use this feature.

    Other Improvements

    •  Client and Server Configuration tool now adds links to Log folder for easier access.
    •  Server Configuration tool now supports specifying a default value for the enableObjectModel data source property.
    • The Server Configuration tool doesn’t reset IIS when Enesys RS Data Extension is configured on Reporting Services 2005. A restart of the Report Server service is done instead.
    •  Improved "In" performances when using SharePoint 2010 by converting the pseudo-CAML element into the new SharePoint 2010 "In" CAML element.
    • A new IncludesAll pseudo-CAML element allows filtering a multi-values column to ensure that returned items contain all the given values.

    Fixes

    • Corrected a bug with the render of specific characters when used in Note fields.
  • Enesys RS Data Extension 3.7.33
  • Enesys RS Data Extension 3.7.33

    Fix:

    • Corrected a bug when designing infoPath statements. In some cases, the designer was looking for the XSN file at a wrong place.
    • Corrected a bug with infoPath statements that prevented setting the useDisplayName attribute to true.

     

  • Enesys RS Data Extension 3.7.27
  • Enesys RS Data Extension 3.7.27

    Fix:

    • Corrected a bug within the infoPath statement that prevented to execute the statement on an InfoPath form that referenced several schemas.
      For example, when using the people picker control, you would have an error similar to "The http://schemas.microsoft.com/office/infopath/2007/PartnerControls:Person element is not declared".
    • Corrected a bug with SharePoint 2007 and Reporting Services 2005 when Reporting Services is configured in SharePoint Integrated mode.
  • Enesys RS Data Extension 3.7.20
  • Enesys RS Data Extension 3.7.20

    Fixed:

    • A bug with SharePoint 2007 and Reporting Services 2005 in SharePoint Integrated mode which prevented the use of the Object Model.
    • A bug which prevented to use the Object Model when doing aSiteCollection queries and one of the sites contained special characters.
    • A bug within the query designer which prevented the creation of aSiteContentTypes statements inside the new statement toolbar.

     

  • Enesys RS Data Extension 3.7.19
  • Enesys RS Data Extension 3.7.19

    New InfoPath features

    Enesys RS Data Extension offers a brand new statement dedicated to InfoPath forms.

    This statement lets you retrieve data from both InfoPath promoted and non-promoted fields:

    Enesys RS Data Extension returns the data using the data type specified in the InfoPath form. However, you can easily select a different data type:

    Using Integrated Security with Forms and Claims authentication

    When used with Reporting Services 2008R2 in SharePoint Integrated Mode, Enesys RS Data Extension 3.7 provides a second data extension (server side) that lets you use the SharePoint Token of the connected user instead of relying on passing Windows identity credentials.

    This new extension ("Enesys RS Token Data Extension") allows you to use "Integrated Security or SharePoint token" with Windows or Forms authentication and Claims based web applications, without the need to use Kerberos.

    Item Versions Performance Boost

    If you have used Enesys RS Data Extension for building reports that deal with item version, you certainly know that this is a time consuming process. The main reason is the limitation of the SharePoint Web Services API in that specific area.

    By using the Object Model, Enesys RS Data Extension v3.7 now provides dramatically improved performances when retrieving item versions in SharePoint integrated mode.

    The following table provides performance comparisons between the version 3.6 and the version 3.7. Those results are based on a query that retrieves 500 items from a list, each item having 4 versions:

      Version 3.6 Version 3.7
    SharePoint Integrated Mode
    Ratio
    500 items
    Retrieving version from 9 fields
    03:10 00:18 10x
    500 items
    Retrieving version from 1 field
    00:38 00:07 5x

    Reference List for RollUpLists statements

    In previous versions of Enesys RS Data Extension, the SharePoint list used to build the target query schema was the first list available. In case all the lists you are aggregating are strictly identical, this is not an issue. But in case some of your lists have additional fields that you would like to be part of the target dataset, you will have to ensure that the first list (which is used to build the schema) has all the necessary fields. Depending on your scenario, this may not be practical to achieve.

    Enesys RS Data Extension 3.7 now allows you to specify a referenceSite attribute that will contain the URL to the site containing the list used to build the schema. Similarly to the relativeSiteUrl, the referenceSite is a URL relative to the data source URL.

    Query Designer Improvements

    Enesys RS Data Extension 3.7 brings various user interface improvements.

    Intellisense

    • Parameters for functions that have the same name as keywords (for example the REPLACE function is also a keyword) are now properly displayed.
    • In order to simplify field selection, Intellisense for SQLite function is now disabled by default. You can re-enable it by clicking on the appropriate button:
    • Corrected a bug which prevented Intellisense for some statements when joining 3 or more statements with "JOIN tableName ON condition".

    New Query Statements toolbar

    A new toolbar was added into the Query Statements panel to allow you to quickly manipulate the statements.

    This toolbar allows you to:

    • Add new statements
    • Go to the Properties form of the selected statement
    • Delete the selected statement
    • Move up/down the selected statement inside the statement list

    New Form for adding statements

    By clicking on the "New" menu item, a form is displayed that lists all the available statements, grouped by category:

    Removed the Columns/Filtering/Sorting tab

    For simplification, the Columns/Filtering/Sorting tab was removed and all its functionalities where moved in order to be available in the main design area.

    The "Query columns" panel was removed.

    You can now reorder the fields inside the Query Statements panel (along with the possibility to delete them):

    The "Columns sorting order" panel was moved into a new "Order By" tab of the Columns tab:

    All the previous functionalities of the control are kept, and this new control offers an enhanced field selector:

    The "Query conditions" tab was moved into the new "Filters" tab of the Columns tab:

    All the previous functionalities of the Query conditions panel were preserved, and some new features were added:

    New advanced filtering control

    Support for moving conditions/groups (up/down and left/right):

    Support for adding parent groups to a specific group:

    Improved field selector by using an autocomplete drop down list:


    Changing the operator no longer changes the value:


    Better support for LookupId and IncludeTimeValue options:


    Showing/Hiding panels

    By default, the Results panel is now hidden. But you can quickly show it by clicking on the appropriate button:

    Similarly, you can quickly show/hide the statement panel by clicking on the appropriate button:

    Other improvements

    • Added two new SQLite collating sequences: UTF8 and UTF8CI. They bring support for UTF-8 comparisons when sorting/grouping data. The UTF8 collating function is case sensitive while the UTF8CI one is case insensitive.

      Usage:
      SELECT foo FROM bar ORDER BY foo COLLATE UTF8
      or
      SELECT foo FROM bar GROUP BY foo COLLATE UTF8CI

      This is useful when sorting/grouping data that has diacritics or non-Latin characters.
    • Corrected a bug which prevented to roll up data starting from a site having spaces in its URL.
  • Enesys RS Data Extension 3.6.31
  • Enesys RS Data Extension 3.6.31

    Fix:

    • Fixed a bug that prevented to query a List which contained some fields with invalid properties.
    • Fixed a bug which prevented to roll up data starting from a site which contained spaces in its URL.
    • Fixed a bug which prevented the use of multivalues parameter inside the sqlData's IN clause in some cases.

     

  • Enesys RS Data Extension 3.6.28
  • Enesys RS Data Extension 3.6.28

    New:

    • XmlQuery statement User Interface has been updated to simplify the usage of report parameters for specifying a URL.

    Fix:

    • The characters accepted inside the name of parameters are now checked for valid values (unicode letters, digits, _, - and #). This allows having a @ character inside the connection string of the sqlData statement.
    • Removed the possibility to sort the columns inside the Columns panel. This option was not only useless (considering dynamic search is available) but also confusing as there was no way of reverting to natural order.

     

  • Enesys RS Data Extension 3.6.26
  • Enesys RS Data Extension 3.6.26

    New:

    • Added support for XML namespaces to the xmlQuery statement. It's now possible to specify a namespace when filtering the XML data through the ElementPath property (ie: //my:element).

    Fix:

    • Corrected a bug inside the Query Designer introduced inside the v3.6.23 that didn't allow you to load a query with IsNull or IsNotNull conditions on Lookup and DateTime columns. Note that it was still possible to edit the query in XML mode and that the bug did not affect the proper execution of a query using such a condition.

     

  • Enesys RS Data Extension 3.6.23
  • Enesys RS Data Extension 3.6.23

    Reporting from Survey lists

    Enesys RS Data Extension offers a new statement that lets you retrieve Survey lists data in a format that makes it possible to build reports. We are also offering a ready-made generic report that can be used with any Survey list.

    Querying Oracle databases

    Starting from the version 3.4, the sqlServerQuery statement allowed you to retrieve data from any SQL Server database. In this new version of Enesys RS Data Extension, the sqlServerQuery statement is renamed to sqlData and is extended by adding support for Oracle databases.

    The behavior is similar, you just have to select between SQL Server and Oracle when you create the statement:

    Then, enter the connection string properties:

    You can now query the database:

    Query Designer - Major Intellisense improvements

    SqlQuery statement is central to Enesys RS Data Extension innovative approach to build sophisticated queries. In this version, we have made several improvements regarding the Intellisense.

    Extended Statement Support

    With the previous versions, only the statement name was provided for sqlData, xmlQuery and sqlQuery statements, you still had to write the field names without any support from intellisense.

    In this version, Intellisense is now provided for fields resulting from any statement:

    • For example, a database queried using the sqlData statement:
    • Or a RSS feed queried using the xmlQuery statement:
    • After having joined SQL Server and SharePoint data using a sqlQuery statement, you can use Intellisense inside a second sqlQuery statement:

    SQL Functions support

    SQLite functions are listed along with their associated parameters and a brief description:

    Parameter description is available when editing a function:

    Better Contextual Support

    Real-time query parsing has been much improved in order to provide contextual  Intellisense support:

    • No statement is selected, the fields are not available:
    • Only the Products statement is selected, only its fields are available:
    • Both statements are joined, all the fields are available:
    • Support for table aliases:

      The "p" name is detected as an alias of the "Products" table; therefore, fields from the Products table are available.

      "pc" is recognized as an alias of the "Product categories" table, its fields are available.

    SELECT and JOIN Snippets

    Two "code snippets" were added for quickly adding SQL clauses:

    • A "SELECT" snippet for inserting a SELECT clause with a FROM clause that selects a single statement:

      By validating (with the Tab key), the snippet is inserted:

      Available statements are proposed for selection:

      Enter/select the desired statement and click on Enter to validate the snippet modification. The caret is then moved just after the SELECT so that you can select your fields:
    • A "JOIN" snippet for inserting a JOIN clause:

      By clicking on the TAB key, you insert the snippet:

      Three placeholders are available for specifying the joined table name and the two columns used as part of the join:

    Using parameters and variables for specifying the URL and the title

    The Properties form of list, survey, mergeLists and rollUpLists statements now has a "Url and Title" tab that allows you to easily change the way you specify the list title and its relative site URL:

    When specifying a parameter, the value is specified into the "DefaultParameterValues" query option:

    The query now has an options statement with the value specified:

    When Reporting Services will retrieve the list schema, it will use this default value, so that you don’t get prompted for specifying the parameter values each time you edit the query.

    Query Designer – User Interface Improvements

    The version 3.6 includes some improvements regarding the User Interface that will enhance your query design experience.

    Adding a list statement

    The dialog box for selecting a list has been completely revamped as shown in the following screenshot:

    Key improvements:

    • Using a data source variable for specifying the relative site URL
    • Filtering lists by name, type and visibility

    Adding a rollUpLists statement

    Similarly to the "Add list statement" dialog box, the "Add rollUpLists statement" dialog box was revamped:

    Key improvements:

    • Improved performances by limiting the data retrieved from SharePoint
    • "On-demand" retrieval of the sub-sites lists
    • Using a data source variable for specifying the relative site URL
    • Filtering lists by name, type and visibility

    Selecting columns

    SharePoint lists may have numerous columns and it may not be easy to go through every column to look for a specific column. We have added some options to the “Columns” tab, as you can see on the following screenshot:

    Key improvements:

    • Dynamic filter of the columns based on their internal and display name.
    • Show/hide the hidden columns with a single click
    • Select/unselect all displayed columns with a single click

    Other improvements

    • The aListPermissions and aSitePermissions statements now use the correct enumeration for the permissions.
    • Improved Null parameter value handling within CAML queries:
      • Eq operator is transformed to IsNull if the parameter value is null.
      • Neq operator is transformed to IsNotNull if the parameter value is null.
    • Null parameter values are properly handled inside sqlData (previously named sqlServerQuery) statements.
    • Parameters may now be used inside the title attribute of the list, mergeLists and rollUpLists statements. This allows you to dynamically change the selected list at report-time, granted that lists have the same selected fields.
    • Corrected a bug with SharePoint 2010 that caused an error to be thrown when retrieving Item Versions for the Editor column.

     

  • Enesys RS Data Extension 3.5.27
  • Enesys RS Data Extension 3.5.27

    Fix:

    • Corrected a bug that would result in an exception when using the stripHtml feature.This is a regression bug introduced in version 3.5.
    • Corrected a bug with itemVersions and SharePoint 2010: when the Editor column was selected inside the itemVersionFields, an error would be thrown.
  • Enesys RS Data Extension 3.5.26
  • Enesys RS Data Extension 3.5.26

    Fix:

    • Corrected a bug with Forms Based Authentication which failed to properly detect the license type in some specific cases, resulting in the inability to query a SharePoint server configured with FBA.
    • Corrected the Object Model detection, which wrongly detected the Object Model in some cases.
    • Corrected a problem that would prevent modifying the objectModelMethod attribute in the rollUpLists statements.
    • Corrected a bug in the Query Designer which caused the toolbar not to be shown when using BIDS 2008 R2 with French language.
  • Enesys RS Data Extension 3.5.22
  • Enesys RS Data Extension 3.5.22

    Changed:

    • Removed the use of temporary files that could conflict with the permissions of the Reporting Services Execution account. This could lead to a "Unable to open database file" error in specific cases.
  • Enesys RS Data Extension 3.5.19
  • Enesys RS Data Extension 3.5.19

    New:

    • Using Object Model for rolling up data:
      In this version, Enesys RS Data Extension can take advantage of the SharePoint object model when Reporting Services is installed in SharePoint Integrated mode (or in Standalone mode when your report server is installed on a Web Front End).
      This can lead to tremendous performance improvement in some scenarios.
       
    • Support for Forms Based Authentication:
      Enesys RS Data Extension is now able to query a SharePoint server using Forms Based Authentication by simply setting the “authenticationMode” Connection String option to “Forms”. This feature is only available in Standard and Enterprise Editions.
       
    • Specifying fields for which to retrieve item versions:
      In previous versions, retrieving item versions was an all or nothing option. Enesys RS Data Extension would retrieve version information for all the selected fields.
      Retrieving item versions being a time consuming process, in this version, we added the possibility to specify the fields for which you need version information.

       
    • Using Data Source variables inside the SqlServerQuery’s connection string:
      In this version, you can now specify “data source variables” inside the sqlServerQuery statement’s Connection String.
      This additional feature makes it easier for moving reports from a development environment to a production environment by simply modifying the shared data source.
       
    • Advanced Properties Form:
      We have added a new “Properties” form that you can access by right clicking on a statement or by clicking on the appropriate button inside the Properties tab:
        

      This new “Properties” form is available for all the statements and offers a better user experience for editing the most common statement properties.


      It automatically validates the data, and displays a small icon with information about the error if the data is invalid:

       
    • New Data Source Connection String options:
      Three new data source connection string options are available to help you fine tune how Enesys Data Extension retrieves data from your SharePoint server:
      • timeout: The time (in milliseconds) to wait for each Web Services call to execute before a timeout occurs. Default value is 300000 (5 minutes).
      • retryTime: The time (in milliseconds) to wait before retrying a call when a timeout occurs. If the value is specified, a single retry will be made, if the value is not specified, no retry will be made.
      • sleepTime: The time (in milliseconds) to wait between two calls made to retrieve the list items (a paging mechanism is used to get items from lists that contain more than 2000 items). If no value is specified, the next call will be made just after the first one is parsed.
       

    Bug corrections:

    • Corrected a bug with itemVersions and Document Library
    • Corrected a bug that prevented the use of a quote character inside the tableName attribute when using the rollUpLists statement.
    • Corrected a bug inside the Query Designer that displayed Intellisense for invalid lookup ID column.
    • Corrected a bug inside the "Add List Statement" form that could lead to an error when trying to add a list.

    For more information about the new features, see the documentation.

  • Enesys RS Data Extension 3.4.7
  • 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
  • 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
  • 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
  • Enesys RS Data Extension 3.4.4

    Fix:

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

  • Enesys RS Data Extension 3.4.3
  • 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.

      image

       

      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:

      image

       

      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:

      image

       

      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:

      image


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

    Value Description
    Default Returns only the files and subfolders of a specific folder. 
    FilesOnly Returns only the files of a specific folder. 
    Recursive Returns all files of all folders starting from the specified folder. 
    RecursiveAll

    Returns all files and all subfolders of all folders starting from the specified folder. 

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

Getting Started

Enesys RS Data Extension in Action

This screencast shows how to build a report from scratch using data from a room reservation application built around a few SharePoint lists.

Evaluating Enesys RS Data Extension

You can easily evaluate Enesys RS Data Extension without installing a Report Server. This article provides comprehensive information for conducting your evaluation.

Customers

  • County of Sonoma
  • Walt Disney Interactive Media Group
  • Farm Credit of Northwest Florida
  • RGA Reinsurance Company
  • Fortress Investment Group
  • GA Dept. of Transportation
  • JP Morgan Chase Bank
  • Lockheed Martin
  • Motorola Inc.
  • National City Bank
  • Visa Corp
  • Dept Prime Minister and Cabinet
  • National Gallery of Victoria
  • Queensland Investment Corporation
  • Queensland Police Service
  • Lockheed Martin UK IS
  • Scottish Parliament - BIT
  • Magna International Inc
  • SaskEnergy