PageHeaderSection showing its containing TextBox twice

[Datamex]

Hi there,

I've been designing Telerik Reports recently, but now I've noticed some strange behaviour. My report is using an ObjectDataSource and in my PageHeaderSection I use a TextBox with its Value property set to "= Fields.Project.Name". Whenever I generate this report I see this TextBox twice above each other.

For instance Fields.Project.Name is equal to "Telerik". My report shows the following:

Telerik
Telerik

____________________________(end of PageHeaderSection).

I just want it to only display "Telerik" once, not twice.

Any idea of what's causing this anomalous behaviour? Thanks in advance!

Regards,
Datamex

[Steve]

Hi Datamex,

We've not been able to reproduce such a problem on our end. Please provide us with more details on how to replicate the issue locally or open a support ticket and attach a sample report that exhibits the problem. Once we review it, we would be able to provide you with more info.

Best wishes,
Steve
the Telerik team

[Datamex]

Thanks for the reply.

Well, my businesslogics call returns an IEnumerable<Activity>.

Each activity belongs to a project. What I want to accomplish is to display the name of the project in my PageHeaderSection, but as I said it's displayed twice. In my DetailSection each activity for the current project is shown. 

For example:
<DetailSection____________________
activity1 ("= Fields.Activity.Name")
activity2
activity3
et cetera.
____________________DetailSection>

As you can see nothing is displayed twice in my DetailSection, albeit the usage of "= Fields.Project.Name" is the same as in my PageHeaderSection. (using "= Fields.Project.Name" or "= Fields.Activity.Name" for the Value property of the TextBox)

As I said in my first post my PageHeaderSection looks like:
<PageHeaderSection____________________
projectname
projectname
____________________PageHeaderSection>

There is only one project, how is it possible that it's shown twice and why is the exact same logic working in the DetailSection, but not in the PageHeaderSection? In my opinion, this is deviant behaviour of the PageHeaderSection, because it's working as expected in the DetailSection.

Hopefully I've provided enough info now.

Looking forward to hear again from you. Thanks!

Regards,
Datamex

[Steve]

Hi Datamex,

Telerik Reporting supports deep object graphs, i.e. business objects with complex properties and there is no problem to use an expression like = Fields.Activity.Name. Moreover as explained in the Understanding Report Sections help article, the page sections are processed by the corresponding rendering extension after the report data has been processed. At this moment the report data source is not available anymore and a data source field placed in a page section would display the first value i.e. = First(Fields.Activity.Name).

Having the above in mind, we do not believe the problem is related to your data source or the fact that the textbox is in the page header and there must be something else in your report causing the textbox to multiply. That is why we would appreciate if you prepare a sample project and attach it in a support ticket or provide a link to it here (remember to remove the assemblies).

Kind regards,
Steve
the Telerik team

[Datamex]

Hi there,

It's not possible for me to submit a support ticket, because of the database you should have to set up, businesslogics which I can't give away and report itself.

I think it's hard to explain it more clearly.

I have a TextBox in my PageHeaderSection with the value = Fields.Project.Name or = Fields.Customer.Name, but the text gets displayed twice. I have a TextBox in my DetailSection with the value = Fields.Project.Name or = Fields.Customer.Name too, but it only gets displayed once as you would expect.

I still can't get a hold of it and really hope you have some ideas I can try out. Thanks in advance!

Regards,
Datamex

[Steve]

Hello Datamex,

We do not need your actual database nor your actual business object. You can use sample/dummy data to prepare a sample report that exhibits the problem, so we can review it.

All the best,
Steve
the Telerik team