Error on Print Preview when multi-column report has document map, and list item data bound with binding to the report datasource

Progress® Telerik® Reporting Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 26 Feb 2019 07:26 by ADMIN

Michael

Created on: 26 Nov 2018 14:45

Type: Bug Report

Error on Print Preview when multi-column report has document map, and list item data bound with binding to the report datasource

When a report fulfills the following conditions :

1. Is Multicolumn;
2. Has DocumentMapText set;
3. Contains a List (data item) with DataSource set with Bindings to a field of the Report DataSource.

and is displayed in PrintPreview mode in the WPF Report Viewer, an exception like :

"Could not register named object. Cannot register duplicate name '_20aa3785775c4790ba0cfa8021bd8433' in this scope.' Line number '1' and line position '2567'. Cannot register duplicate name '_20aa3785775c4790ba0cfa8021bd8433' in this scope." is thrown.

3 comments

ADMIN

Milen | Product Manager @DX

Posted on: 26 Feb 2019 07:26

Hi Michael,

The issue is fixed with the R1 2019 SP1 release: https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r1-2019-sp1-13-0-19-222

Regards,
Milen
Progress Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items

ADMIN

Todor

Posted on: 01 Feb 2019 13:26

Hi Michael,

Our work items are prioritized based on multiple factors. Up to the official release, our developers are mostly concentrated on implementing new features - for R1 2019 there were quite a few. For the Service Packs, they are dealing mostly with bug fixing. Our R1 2019 SP1 release is scheduled for the second half of February 2019. I hope we will have sufficient resources to address also this issue.

Regards,
Todor
Progress Telerik

Michael

Posted on: 28 Jan 2019 07:21

It was planned to fix the bug for the middle of January.

The status is still set to new.

When can we expect the problem to be resolved?

Thanks in advance