Home > Products > BPC PowerForms > Knowledge Base > SQL Queries > SQL Queries in PowerForms

SQL Queries in PowerForms

PowerForms HTML supports direct SQL Queries that can be used to provide lookup data for lookup controls (such ComboBoxes).


For security reasons, the actual sql query is not defined inside PowerForms designer but another setup model has been adopted :

  • 1. A custom list should be created server-side.
  • 2. The definition should be stored there (including ConnectionString, SQL Command and parameters) in XML format
  • 3. Inside the PowerForms designer, the user references the sql-query entry of that list and binds parameter values using static data or dynamic control values


Step A : Create the custom list to store queries

  • 1. Create a new custom list in your site collection (for example name : PowerForms SQL Queries)
  • 2. Add a new column called "QueryXML: (multiple lines of text, PlainText)
  • 3. Setup security for your list as you may want to restrict users from viewing query details (query is executed using elevated permissions)


Step B : Create a query definition

Add a new item inside the list. Set the title of the item.

Inside the QueryXML field, you should use the following xml schema to define the query.


<Query Elevated="true">
<ConnectionString>Provider=SQLOLEDB;Data Source=.;Initial Catalog=WSS_Content;Integrated Security=SSPI;</ConnectionString>
<SQL>select ID, Title, Priority, Type, StartDate from Customers where ID=?</SQL>
<Parameter Name="ID" Type="Number" />

The Elevated="true" parameter forces the execution of the query to be done under the application pool account. This is needed in case you need to access your database using windows authentication. If you are using SQL/native database authentication then this is not needed.

Note that the schema contains 3 main properties :


This contains the OLEDB connectionstring to the database


Contains the sql command of your query. If a stored procedure is to be called, you should add the attribute Type="SP" to the Query element. For example : <Query Type="SP">


You can define unlimited number of parameters in your query. Values for these parameters are provided by the form during query execution.

Parameter types supported : "Text", "Number", "DateTime".


Step C : Setup the query in PowerForms designer

A new section inside the designer has been added to configure SQL Queries.

There you must reference the Query List URL and Query List Name, set the Query Name (which corresponds to the Title column) and setup parameters (that should be already defined in the query xml)

In our example, we want to set the parameter with the value ({value:c_Customer}) of a form control.


Step D : Bind the query to your control

Add a combobox control on your form.

Inside the Looup Details section, you should select that the lookup values come from a SQL query, select the query from the provided list and set the Display and Value fields of the control.

If a single field is required (i.e. Title) use that field for both properties (Display and Value members)/

NOTE : PowerForms provide automatic refresh to the lookup control every time a control value that affects the query parameter, is changed by the users.


Example : Calling a Stored Procedure

We assume we have a table (named Products) containing our product list.

Columns : ID (int), NAME (nvarchar), DESCRIPTION (nvarchar)

We create a stored procedure to retrieve products :


@ID int = null

As you may notice, we have provided an optional parameter in order to retrieve a single record if necessary.

Now to define the query xml we would have to provide something like the following :


<Query Type="SP">
<ConnectionString>Provider=SQLOLEDB;Data Source=.;Initial Catalog=TestDB;Integrated Security=SSPI;</ConnectionString>
<Parameter Name="ID" Type="Number" />

Notice the Type="SP" attribute of the query xml element. It is important to use this attribute in order to call a stored procedure.

Now we setup the query inside the PowerForms designer and test the results:

Test the optional parameter by setting "ID;1" inside the Parameters propery.

Now we bind the query to a ComboBox control to examine the results :

The combobox in action :

Instead of a ComboBox control, RadioButtons can be used to display SQL Query results :