An item with same key has already been added

[BC]

Hi,

I have installed Reporting Q3 2009 on Windows 7 and using it in VS 2008, SQL 2005 and .Net 3.5 environment. I have created Reports class library and created a report which runs fine when I previewed it. However, when I added it to the web project, I keep getting "an item with the same key has already been added" on the line below
            RenderingResult result = reportProcessor.RenderReport("PDF", reportToExport, null);
I have used ReportViewer and also tried exporting programmatically to PDF format.

Any help is greatly appreciated.

Thanks,
Bhargavi.

[Peter]

Hi Bhargavi Chukkapalli,

This is a generic .NET error that is not directly related to Telerik Reporting and you can find numerous threads on it in various scenarios. In the context of Reporting, it could happen when you try to add two or more items with the same ID/Name e.g. you have a textbox (textBox1) and in your code you try to add another one with the same name.
Please review your code and if you are unable to find the duplicate, send us a sample runnable project that replicates the issue.

Kind regards,
Peter
the Telerik team

Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.

[BC]

Hi,

Thanks for your response. I tried your suggestion checking for any duplicate names and could not find anything in that area. However, I was able to resolve by changing the way report parameters are assigned inside the aspx code. I was creating a report parameter object and setting it's name, value and then assigning it to the report. For some reason this was the cause of the error I was receiving. I changed to do it all in one line like below and the issue got resolved.           

reportDoc.ReportParameters["PDID"].Value = this.PDID;

[MGrassman]

I had this same error when I upgraded to 2010 Q2.  Q1 worked just fine with the same report.  the problem ended up being I was using a report book and the paramaters were the same for both reports.  I went in and changed the paramters on one of the reports and and everything worked fine. 

Should I have set the parameters differently in the report book?

ReportViewer1.Visible = districtRecId.ToString() != "0";
            BPB.Reports.DistrictStatsFSDView headerReport = new BPB.Reports.DistrictStatsFSDView();
            headerReport.ReportParameters["DistrictRecId1"].Value = districtRecId;
            headerReport.ReportParameters["BudgetYearGroup1"].Value = Convert.ToInt32(ConfigurationManager.AppSettings["BudgetYearGroup"].ToString());

            BPB.Reports.FSDBusinessPlan detailsReport = new BPB.Reports.FSDBusinessPlan();
            detailsReport.ReportParameters["DistrictRecId"].Value = districtRecId;
            detailsReport.ReportParameters["BudgetYearGroup"].Value = BudgetYearGroup;
            ReportBook reportBook = new ReportBook();
            reportBook.Reports.Add(headerReport);
            reportBook.Reports.Add(detailsReport);

            ReportViewer1.Report = reportBook;

[Steve]

Hi MGrassman,

As noted in the Report Book documentation, Telerik Reporting provides a mechanism known as parameter merging. The rule for merging parameters is straightforward - if the Name and Type of two (or more) parameters from different reports are the same, then they are considered equivalent and are displayed as a single parameter in the parameters area.
So having the same parameters in two different reports should definitely not cause such problems and we were not able to reproduce such behavior. However a somehow related issue was fixed in the latest internal build, when you use the same report several times in a report book with different value of a parameter and this parameter was marked as Mergable=false, but according to your code this is not the case.

Sincerely yours,
Steve
the Telerik team

[Michael weinberger]

I have found another reason for that error in latest release.
If your dataset contains two columns with the same name (like Table1.Id, Table2.Id, without aliases) you get the same error when trying to see report or even preview the dataset.

Other reporting solutions prefixes the extra fields like Id1, etc. At least a better error message should be there :-)

Thanks

[Preston]

This was exactly the problem for me. I was using an ID as one of the report parameters, and the stored procedure was returning the same id twice in the join. 

Thanks for the post!