Page 1 of 2

Making a GroupHeaderBand a component?

Posted: Tue Dec 19, 2023 5:44 pm
by ericp
Due to the complexity of my report, I needed to create a GroupDataBand + Databand to combine 2 objects in my JSON. Part of my report is comparing current data vs previous data. I am currently able to do it by having these GroupHeaderBands separate (in my second screenshot), but what I really want it to do is to have them show grouped and not all current data and then all previous data.. (almost like a component if it were a regular Databand)

When I try to move the GroupHeaderBand up together, it does not display correctly as it seems to need the Databands next to the GroupHeaderBand to show the correct information. (as you can see in the screenshot with red markings, it's just repeating the first project number)

Re: Making a GroupHeaderBand a component?

Posted: Tue Dec 19, 2023 10:55 pm
by Lech Kulikowski
Hello,

Please send us a sample report with test data for analysis. Also, please provide the necessary result. We will try to find a solution for you.

Thank you.

Re: Making a GroupHeaderBand a component?

Posted: Thu Dec 21, 2023 6:49 pm
by ericp
Hi Lech, please see the attached for the MRT file that we're working on.

Re: Making a GroupHeaderBand a component?

Posted: Thu Dec 21, 2023 10:51 pm
by Lech Kulikowski
Hello,

We couldn't reproduce the issue. Please check the last release build.

Thank you.

Re: Making a GroupHeaderBand a component?

Posted: Fri Dec 22, 2023 4:13 pm
by ericp
Lech that is how I left the mrt file. What I want to do is to make Groupdataband2 as a subcomponent to Groupdataband1. As you can see right now we’re showing all of the info for Groupdataband1 and then info for Groupdataband2. Ideally we want it to be like this format:

Groupdataband1 object 1
Groupdataband2 object 1
Groupdataband1 object 2
Groupdataband2 object 2
Etc..

Right now for format is doing

Groupdataband1 object 1
Groupdataband1 object 2
Groupdataband2 object 1
Groupdataband2 object 2

Re: Making a GroupHeaderBand a component?

Posted: Sun Dec 24, 2023 1:02 pm
by Lech Kulikowski
Hello,

Sorry, maybe we did not exactly understand your task. Your groups are the same. Could you sho the necessary result?

Thank you.

Re: Making a GroupHeaderBand a component?

Posted: Tue Dec 26, 2023 8:51 pm
by ericp
Please see the screenshot below as I try to better explain:

Currently in the MRT File, I have 2 separate GroupHeaderBands (1 for CurrentProject Info and 1 for PreviousProject Info) I'm trying to create a table that puts them right next to each other so that it is easier to compare the difference between Current and Previous. I have been unable to do this (as you can see in the current MRT file, it displays all CurrentProject Info and then all PreviousProject Info. This is hard because as our list gets longer, we will have to scroll up and down more in order to see the differences between the two.

Re: Making a GroupHeaderBand a component?

Posted: Wed Dec 27, 2023 8:34 am
by Lech Kulikowski
Hello,

In that case, you should use master-detail construction instead of the grouping.
You can add master source with all Object ids and two details Current and Previous.

Thank you.

Re: Making a GroupHeaderBand a component?

Posted: Wed Dec 27, 2023 6:01 pm
by ericp
Hey Lech, I have tried and having issues doing it. Could you please send an example?

In an earlier ticket you mentioned to use Grouping: viewtopic.php?t=61429

So if I try to use the Master-Detailed Source, I run into that same duplicate issue.

Re: Making a GroupHeaderBand a component?

Posted: Thu Dec 28, 2023 9:37 am
by Lech Kulikowski
Hello,

Please check the modified report.

Thank you.