Microsoft Dynamics 365 Blog

A CRM MVP, our guest blogger David Jennaway is the technical director at Excitation. Excitation is a Microsoft Gold Partner in the UK that specializes in delivering Microsoft Dynamics CRM solutions. He has generously placed all the code for this post on

With pre-filtering, CRM offers a powerful way to produce context sensitive reports based on the selected records in a grid, or the current record in a form. In this article I’ll cover an alternative approach that can be used to display report content within an IFrame on a form, or provide a simple way to run a report from a toolbar button or menu item in CRM.

How it works

SQL Server Reporting Services provides a means for running and rendering a report by accessing a URL and passing all relevant report parameters and rendering options in the query string of the URL. CRM offers a simple means to pass the current entity type, name and instance ID as parameters on the query string when accessing a page in an IFrame, or through a toolbar button. The approach covered in this article combines these 2 features.

Creating the report

The main example I’ll use for this article is a report that will be used in an IFrame on the CRM account form. This will display a summary of the total business done with that account, summarising opportunity and case information. This example has been created for SQL 2000 Reporting Services, using Visual Studio 2003, but works identically for SQL 2005.

We will need to pass the instance ID of an account to the report as a parameter. This will be passed by the IFrame control in the CRM form, and is of the form:


When passing parameters to a report for URL access, the parameter name in the report must match the corresponding value on the query string. Additionally, each value on the query string must either control the report rendering (see later) or exist as a report parameter. Therefore we need to create 3 parameters for the report: id, type and typename.


As Reporting Services doesn’t offer a Guid datatype for parameters we’ll set the id parameter to be of type string. Although we don’t need to set default values, I tend to add in an id of a valid account to simplify testing in the development environment.

We can now use the id parameter in our SQL query as normal in Reporting Services


Here is the SQL statement I’m using. Note that the @accountid parameter is cast as a uniqueidentifier SQL type.

SELECT statuscodename AS Status,

SUM(CASE WHEN isnull(actualvalue, 0) <> 0 THEN actualvalue

    ELSE estimatedvalue END) AS Value

FROM FilteredOpportunity

WHERE (accountid = CAST(@accountid AS uniqueidentifier))

GROUP BY statuscodename

Here is the full report rdl (I’ve kept formatting to a minimum to reduce the file size). Change the connection string in the Data Source to that of your server.

<?xml version=”1.0″ encoding=”utf-8″?>

<Report xmlns=”” xmlns:rd=””>




      <Table Name=”table1″><Style />




                <TableCell><ReportItems><Textbox Name=”textbox2″>




     <TableCell><ReportItems><Textbox Name=”textbox3″>











<TableCell><ReportItems><Textbox Name=”Status”>

<Style /><ZIndex>1</ZIndex><rd:DefaultName>Status</rd:DefaultName><Value>=Fields!Status.Value</Value>


<TableCell><ReportItems><Textbox Name=”Value”>

















    <DataSource Name=”Excitation_Test_MSCRM”>




    <ConnectString>initial catalog=Excitation_Test_MSCRM</ConnectString>







<DataSet Name=”Excitation_Test_MSCRM”>


<Field Name=”Status”><DataField>Status</DataField><rd:TypeName>System.String</rd:TypeName></Field>

<Field Name=”Value”><DataField>Value</DataField><rd:TypeName>System.Decimal</rd:TypeName></Field>




<CommandText>SELECT statuscodename AS Status, SUM(CASE WHEN isnull(actualvalue, 0) &lt;&gt; 0 THEN actualvalue ELSE estimatedvalue END) AS Value

FROM FilteredOpportunity

WHERE (accountid = CAST(@accountid AS uniqueidentifier))

GROUP BY statuscodename</CommandText>

<QueryParameters><QueryParameter Name=”@accountid”><Value>=Parameters!id.Value</Value></QueryParameter></QueryParameters>








   <ReportParameter Name=”id”>





<ReportParameter Name=”type”>






      <ReportParameter Name=”typename”>








Publishing the report

The report can either be published via CRM, or directly to Reporting Services via Report Manager. As reports created this way are not intended to run in the same way as other CRM reports, I tend to create a separate folder in Reporting Services for these reports, and deploy them directly in Report Manager. However, all that really matters is that you know the path to the report in Reporting Services.

Accessing the report from a browser

The syntax for rendering a report from a url takes the following form:



http://server/reportserver is the url to the report server (not the Report Manager)

/Excitation+Test_MSCRM/Account+Opportunity+Summary is the path to the report, which you can find via Report Manager.

Using the above url will render the report, but with extraneous information. The following additional parameters will remove the toolbar and parameter list:


The first of these removes the toolbar and parameter list, and the second ensures that the report is run with new data each time it is accessed

Creating the IFrame

So, we can now add an IFrame to the CRM account form with the following url:


To pass parameters, select the ‘Pass record object-type code and unique identifier as parameters’ check box.

We can now publish and test the form


Launching a report from an ISV.Config button

A very similar approach can be used to launch reports via ISV.Config. There is one important difference; the parameters are passed slightly differently, for example:


Therefore the parameters in the report need to be defined as oId, oType and oTypeName.

Also, when you specify the report url in isv.config.xml, any ampersand (&) characters in the url need to be encoded as &amp;

It is possible to specify the output format of the report via the url. For example, add the following to render the report as a pdf document:


Further ideas

Another use of this technique with CRM data would be to show related data on a form. An example would be to display on the opportunity form the address information for the opportunity’s customer.

The example given here only accesses data in the MSCRM database, but it is perfectly possible to reference data in other data sources in the report. In one recent example I worked on we used the same technique to display account financial information (such as current credit limit and rating) from Great Plains in the CRM account form.

David Jennaway


Links – URL access with SQL 2000 reporting services – URL access with SQL 2000 reporting services – passing parameters to an IFrame in CRM 3.0 – modifying in ISV.Config CRM 3.0

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!