The versions are slightly out of date, but know that RDL files are created via the Report Designer (currently built on VS2010 shell) and RDLC files are created normally through VS. RDL and RDLC formats have the same XML schema. NET reports, fast, with the Visual Studio add-in. Pick from layout-driven page reports, scrolling RDL reports, and code-based section reports to create a.

Not 100% sure if this is the right forum. I have a report I need to edit, have visual studio 2012, installed the correct frameworks, created a BI solution, added the exported RDL as a report. I added a shared data source to match the name required in the report, test's okay. Added shared datasets to match the required datasets in the report, with the sql queries provided in the xml of the rdl. When I go to preview, the parameter drop downs aren't autopopulating the values in the datasets defined for that parameter.

For a dataset, for example, 'Division', if I go to the Query Designer in visual studio and run the query for that dataset I have, it produces the correct fields, with the correct values that I want to populate the default parameter list, however it does not actually do this when I preview the report from within visual studio. Example XML that defines that parameter: String Division kore_divisionid Entity Division kore_divisionid kore_name true What I see in visual studio: What I see in the report from the CRM pre-export (whiteout applied for obvious reasons): Please let me know if anything was unclear, any potential solutions, or if this is the wrong forum and where the correct place to post this would be.

Hi, A few points: 1. If you are are writing reports for CRM2011, only Visual Studio 2008 is supported by the BIDS Extensions for fetchxml - if you are using SQL queries then it is mostly ok to author in VS2012 although I've had strange issues that has always made me revert back to use VS2008. The most common reason for data not being present when testing reports is that the query is against the Filtered Views, but you are not authenticating against a CRM user. This will mean that the filtered views will return no records due to you not having a CRM Role. Even if you have dbo admin right on the database, unless you have a CRM user that maps to the identity you are logging on as, you'll get no results. You shouldn't need to add a new connection/datasource - it should already be there named 'CRM' - when adding datasets, you should simply reference the 'CRM' datasource.

To check that the issues isn't to do with your parameter configuration - I always just drop a simple table on the report and set the parameter source as the data source. Hi, A few points: 1.

If you are are writing reports for CRM2011, only Visual Studio 2008 is supported by the BIDS Extensions for fetchxml - if you are using SQL queries then it is mostly ok to author in VS2012 although I've had strange issues that has always made me revert back to use VS2008. The most common reason for data not being present when testing reports is that the query is against the Filtered Views, but you are not authenticating against a CRM user. This will mean that the filtered views will return no records due to you not having a CRM Role. Even if you have dbo admin right on the database, unless you have a CRM user that maps to the identity you are logging on as, you'll get no results. You shouldn't need to add a new connection/datasource - it should already be there named 'CRM' - when adding datasets, you should simply reference the 'CRM' datasource. To check that the issues isn't to do with your parameter configuration - I always just drop a simple table on the report and set the parameter source as the data source.