Release Notes for SQL View

Release Notes for SQL View

NOTE: Release Notes will open in a new browser tab

WSSv3/MOSS SharePoint 2010 SharePoint 2013
Release Notes Release Notes Product not available
Microsoft ended mainstream support for SharePoint 2007 in October 2012. See Microsoft’s Lifecycle Support Policy.
At that time, Bamboo stopped enhancements to our SharePoint 2007 product line, but continues to provide support and bug fixes to customers with active support contracts until October 2017. Previously purchased licenses will continue to function after October 2017, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2007 products in October 2016 to ensure customers will be eligible to receive support for at least one year after purchase.
Microsoft plans to end mainstream support for SharePoint 2010 in October 2015. See Microsoft’s Lifecycle Support Policy. At that time, we will stop any enhancements for our SharePoint 2010 product line but will continue to provide support and bug fixes for our SharePoint 2010 products to customers with active support contracts until October 2020. Previously purchased licenses will continue to function after October 2020, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2010 products in October 2019 to ensure customers will be eligible to receive support for at least one year after purchase.

Bamboo Solutions has also begun releasing Bamboo Apps to the SharePoint Store, for additional details, see the SharePoint Apps & Mobile products page where you can get the latest info about each of our Apps as they release to the Microsoft Store.

A separate installation package and license key is required for SharePoint 2013 deployment. For additional details, review the following knowledge base articles:

Understanding Bamboo Releases:

  • Bamboo offers Trial, Basic and Premium support.
    • Free Trial support expires after 30 days.
    • For more information about Basic and Premium support, please see the Support Plans page.
    • There may be a fee to upgrade from a major version to another.

See Also:

Overview of SQL View Web Part

Overview of SQL View Web Part

hw04010.jpgSQL View, using the SharePoint Object Model API, searches for and displays all the lists from the top-level site (where the web part is installed) to all its sub sites. The user can only see the lists that he/she has permission to access. The user can then select the fields within the list to be included in the SQL query statement, including external fields referenced by a lookup field.

A SQL query statement is generated for the selected fields, which can then be copied and pasted to a report tool, or a SQL View can be created automatically in the SQL database to be used by the report tool.

Overview of SQL View Configuration

Overview of SQL View Configuration

After SQL View is added to the page, two configurations are necessary:

  1. the location of the bamboo.view.ascx file must be identified
  2. the database connection must be configured if a database view is to be created automatically.

This step is required only if you want SQL View to generate the view for you automatically. To customize SQL View:

Step Action Result
1. On a Web Part Page, click Modify Shared Page.
2. Select Modify Shared Web Parts on the upper right drop-down arrow of SQL View.
3.

Under the Miscellaneous section you will see an option to enter a custom string of characters that the web part needs to generate the view from SQL directly into the content database.

SP Content DB Connection String: Enter the custom connection string that the Web Part needs to generate the view.

hw04008.jpg

How to Use the SQL View Web Part

How to Use the SQL View Web Part

Go to the page where SQL View is installed and generate the SQL query statement by following these simple steps:

Step Action Result
1. In the Select Site drop-down list, pick the site where the Task list was created. hw04010.jpg
2. Select the desired list in the Select List drop-down list.
3. Enter a name for the view in the View Name text box.
4. Check the Validate Lookup Fields check box if you want to include referenced fields in your query. If checked, they will appear in the Select Fields list.
5. Select the fields you want to return in the query by highlighting them in the Select Fields list. Select more than one by using the Ctrl or Shift keys while selecting.
6. Check Generate View in Database check box if you want to automatically create a view in the SharePoint content database.
7. Click Generate. A message will be displayed to indicate success or failure.

How to create a SQL query statement that can be embedded into a Crystal report

How to create a SQL query statement that can be embedded into a Crystal report

The following procedure describes how to create a SQL query statement that can be embedded into a Crystal report, running from your client desktop.

Step Action Result
1. Install SQL View as described in the Installation section and configure the Web Part to make sure it can communicate with the SharePoint content database as described in the Configuration section.
2. Go to the page where SQL View is installed and generate the SQL query statement by completing as shown here:

hw04016.gif

  • In the Select Site drop-down list, pick the site where the Task list was created.

  • Select “Tasks” in the Select List drop-down list.

  • Enter a name in the View Name text box. To create a view in the SharePoint Content database, this view name must be unique. If a view with a similar name already exists, then the Web Part identifies it and view is not created. Note that the existing views are not deleted or dropped.

  • Select the Validate Lookup Fields check box so the query will perform the joined query to get the name of the assigned user.

  • Select the fields you want returned in the query.

  • Check the Generate View in Database check box and click the Generate button.

3. After clicking the Generate button, check the database to make sure a view was created, using SQL Enterprise Manager as in this example: hw04026.gif
4. Create a data source on your desktop that provides the connection to the SharePoint content database where the task list exists. You can do this on a Windows XP desktop by selecting Start > All Programs > Administrative Tools > Data Sources (ODBC). hw04028.gif
5. Add a new data source, using the SQL Server driver. hw04030.gif
6. Enter the name of the data source and select the appropriate SharePoint server name. hw04032.gif
7. Fill in the account logon with the appropriate permission to read the content database. hw04034.gif
8. Select the correct table name for the SharePoint content database. hw04036.gif
9. Test the data source you just created to make sure that access permission to the table is working correctly. You should now have a new DSN (WSS-RD1 in this example) listed in the ODBC data sources list.
10. Startup Crystal Reports, create a new report and select a new ODBC driver. hw04038.gif
11. Expand the ODBC tree, select the DSN that you just created in step 3, supply the correct user information, and then select the SharePoint content database. hw04040.gif
12. Once the connection to the database is completed, you are presented with the tables, views and stored procedures in the SharePoint content database. Expand the Views node in the tree, and select the SQL View name that was created in step 1 above (TaskView in this example). hw04042.gif
13. You will now be able to see the fields that were selected in SQL View above, which is ready to be dragged and dropped on to the report Design View. hw04044.gif