In my one-page report I have a header and footer. But then I need the main body to split into two repeatable sections and I only manage to create subsections or grouping sections of my first and only repeatable section. In my database have a Master table (M) with 2 independant details tables (D1 and D2). The details tables together do not have more rows than everything will fit on one page. So I want my report to be like this:
Page Header (M)
Repeatable Section (D1)
Repeatable Section (D2)
Page Footer (M)
But I cannot find a way to add the repeatable setion for D2. No matter where I click or drop D2 fields it will always mess with D1 and create subsections or group sections.
What am I missing?
Edit: spelling
I still don't know how to do in the on the report design UI, but I opened the igr file and hacked the XML to get my second repeatable section and got it to work.
This is not how I want to do it so if anyone knows how to do it in the UI, please let me know.
Hi,
I created a data object of two collections to simulate your database tables.
And I added a section containing two subsections to my report. Then I added my data object, which is an enumeration, as a DataSource and set it as the source for the section and for each subsection. Then in each subsection I added a table with its DataContext set to one of the underlying collections. (In my sample, I called them First and Second. So the first subsection's table has a DataContext of First and the second subsection's table has a DataContext of Second.)
Each table is a repeatable element, showing the data from its appropriate collection from within the data source. And since there isn't much data to show, I can show both subsections on the same page.
If your data was such that you could use Grouping based on some field in your data, you would perhaps have the repeatable sections you were looking for. Each subsection could have its own grouping if that was required and the table or other elements would be included in the group.
Please let me know if this sample helps.
Greetings!
Yes, I looked at the samples and analyzed the answer. But unfortunately it is not what I need. In my first post I mentioned the Master-Detailed view of it, but actually in the database there are no SQL relations between the master data and the two details data. So I cannot use Groups or Subsections. What I do is that I have three DataSources in the report. The first DataSource deliver just one row which is used in the header using the =First(... syntax. The two sections each connects to a different DataSource and loops through the rows from that DataSource (not using a Table control) using the =Fields. ... syntax too display the data.
But I still cannot find a UI way to create those multiple independant sections on tha page.
My recent report encountered the same problem on a totally different way. The body part (between page header and page footer) consist of 18 different sections all with their own datasource and layout. A master datasource with 18 boolean values then indicates if the section should be visible or not depending on what sections the user have selected. To solve this, each of the sections have a visible condition set, =First(Fields.Boolean1, DataSources.SectionSelector), and it works perfectly. If all sections are visible, the report uses about 6 pages and paginating as it should.
But I could not figure out how to add the extra 17 sections beside the default in the report. I had to open the .igr file again in the VS XML editor and copy the first section 17 times. It works and the designer handles it just fine when I open the modified XML file. But still it would be nice to be able to do this inside Visual Studio in the Report Designer.
See this image for my first Master-Detail*2 report. The two section "Accept01" and "Accept03" are indepenedant of each other and on hte same level. No group or subsection.
I hope that the information I provided is helpful to you and that you added your idea to our product idea site.
Please let me know if there is anything I can help you with.
Your image didn't attach.
However, as I understand your requirements, you can use the one section as the body of the report and add all of the elements (labels, tables, etc.) without adding subsections or groups.
Each element in the entire section can be bound to any of the sql sources you have defined. Or in your case a "group" of elements could be bound to the same data source. And you can bind the Visibility property of each element to the specific value in your database to control the visibility of that "group" of elements. If you need to have repeating elements within a "group", you can use a table and define rows as containing specific values like headers or data fields that would expand depending on the number of rows retrieved from a database.
It doesn't sound as if you need it but you can also add pagebreaks between "groups" of elements.
I would also recommend that you add your idea concerning creating multiple sections that can be bound to specific data sources and whose visibility property would control all of the elements in that section to our product idea site<http://ideas.infragistics.com>.
The Product Ideas site allows you to suggest new product features, new functionalities in existing products and controls, and even request new controls and products altogether. Members of the Infragistics Community can then vote for the features and suggestions they want to see added to the products, resulting in the most popular features bubbling up to the top. When planning new releases, our Product Management team will look at the most popular features and use your feedback to prioritize upcoming work.
This new Infragistics Product Ideas site is simple to use and we encourage you to take a look at it today:
1. Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
2. Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
3. Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and you can even track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Please let me know if you have any questions.