This is a migrated thread and some comments may be shown as answers.

Excel Export Error

4 Answers 70 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
devoas
Top achievements
Rank 1
devoas asked on 07 Mar 2011, 08:10 AM
Hello,

We are facing problem in Excel Export and giving message 

Attempting to get range {3,21}-{7,1},Merged=False,Parent=rptSummary[0], that intersects with an already merged range.

We have noticed that there is a textbox, causing problem if we reduce the width below  0.34in then it throw error otherwise not. Please confirm if there is any limit that textbox width cannot be less than this.

Version: 2010.3 1221

Thanks,
devoas,




4 Answers, 1 is accepted

Sort by
0
Deva
Top achievements
Rank 1
answered on 22 Aug 2011, 04:57 PM
We are getting this same error, the report renders fine, but when we go to export it to excel, we have several subreports, that get their Datasource's from : but the second time through the Datasource is null... any ideas?
private void subReportGeneralStatuses_NeedDataSource(object sender, EventArgs e)
{
    this.subReportGeneralStatuses.ReportSource.DataSource = (this.DataSource as General).LoanStatuses;
}

0
Peter
Telerik team
answered on 23 Aug 2011, 11:49 AM
Hi Deva,

Generally when using report events you should utilize only the processing report items. However the events approach is used as last resort and in your case our suggestion is to utilize bindings. For example you can set up the SubReports.ReportSource.DataSource property to the master report's collection as shown in the following example:

Property path  Expression 
 ReportSource.DataSource  =Fields.LoanStatuses

Regards,
Peter
the Telerik team

Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>

0
Deva
Top achievements
Rank 1
answered on 23 Aug 2011, 01:14 PM
Hi Peter,

We do use bindings at the field level for the data on the subreport, but for that to work the DataSource needs to be set... I guess I am confused as the report renders properly, and exports to pdf, rtf, but when it goes to export to excel it seems that the events dont filre in the same order and as a result my _NeedDataSource event blows up null reference exception, so initially I thought I could just check for the null reference, and do nothing if the datasource is null, but then I still get the error : Attempting to get range {xx,xx}-{xx,xx},Merged=False,Parent={somereportname}, that intersects with an already merged range. (though my message is in a cropped window).  We are running with the latest reporting package, and unless we just missed this use case in our prior testing, this used to work 1-3 versions ago...

Our scenario: we have a parent report with 3 child / sub reports on them... in the parent report's NeedDataSource event, we set the 3 subreports datasources as so:
this.DataSource = _DataSourceCache;
 
this.subReportFundingCurve.ReportSource.DataSource = (_DataSourceCache as AssumptionsClass).FundingCurveInformation;
this.subReportGeneral.ReportSource.DataSource = (_DataSourceCache as AssumptionsClass).GeneralInformation;
this.subReportProduct.ReportSource.DataSource = (_DataSourceCache as AssumptionsClass).ProductDetails;

then in each sub report, we have this:
private void subReportGeneralStatuses_NeedDataSource(object sender, EventArgs e)
{
    if (this.DataSource != null)
        _DataSourceCache = this.DataSource;
    if (_DataSourceCache != null)
        this.subReportGeneralStatuses.ReportSource.DataSource = (_DataSourceCache as General).LoanStatuses;
}

0
Peter
Telerik team
answered on 26 Aug 2011, 09:15 AM
Hello Deva,

This error occurs whenever you have overlapped items but data binding error should't raise such exception. As described in the Design Considerations for Excel Rendering help article, overlapped items are not allowed in excel. So in cases like yours, whenever you plan to export to excel you need to make sure that you do not have overlapping items.

If the above is not valid for your report and you're still having problems, please prepare and send us a sample report that exhibits the problem. Once we review it, we would be able to provide insight on the matter.

Kind regards,
Peter
the Telerik team

Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>

Tags
General Discussions
Asked by
devoas
Top achievements
Rank 1
Answers by
Deva
Top achievements
Rank 1
Peter
Telerik team
Share this question
or