Hi,
I have a Toggle Button on the header of the parent group (Group Name in example) which when I expand does not reflect on the toggle buttons of the child (BZ Liquor Eat In etc in the example). Same with the toggle button on Department and its sub group toggle buttons. I have attached screen shots for better understanding.
They all work fine individually, just that when I expand / collapse all, the individual buttons need to change as well. Any help would be appreciated. Thank you
11 Answers, 1 is accepted
You can try the suggestions in the Expand/collapse All thread.
Regards,
Nasko
Telerik by Progress
Rank 1
Hi Nasko,
Thank you for getting back. I did use the method demonstrated in the thread to set my Expand All button, in my case it is the "Group Name" header textbox (see CollapsedMode.png). My target for the toggle action is the same as the toggle for textbox [=Fields.GroupName] (please see ReportDesign.png for clarity).
Because it is at header level, it expands the departments for all groups (see ExpandedMode.png) which is exactly what is want. But the toggle button next to each group name (for example "BZ Liquor Eat In") still shows collapsed mode even though it is expanded.
In simple words, currently both the textboxes ("Group Name" header & [=Fields.GroupName] have the same target for the toggle action which is departmentDescription (TableGroup) but the header expands the departments for all groups whereas the other expands the departments for just for that group. All ok except the toggle button sign. Hope I make sense.
Thanks
You can change the toggle state by clicking on this checkbox.
Regards,
Nasko
Telerik by Progress
Rank 1
Hi Nasko,
I have that checkbox unchecked for both the header (Group Name) and the [=Fields.GroupName] (for example "BZ Liquor Eat In") as initially all the Departments of all groups are in collapsed mode. I can expand just one group and see its Departments or expand all groups by pressing the toggle in the header. Hence both the header toggle and the [=Fields.GroupName] needs to be in collapsed mode initially.
The problem is when i click the header toggle and it expands all groups' departments, the toggle in the individual group names needs to change to expanded mode automatically which is not happening.
Rank 1
Hi Nasko,
I created a basic report with AdventureWorks data so that you can test it from your end as well but unable to attach a .trdp file, hence details below.
As you can see in Collapsed.png , the toggle button on the Category header and the toggle buttons on the individual category names (Accessories/Bikes/Clothing/Components) are all in collapsed mode initially. When I click on the toggle button next to a category name, say Accessories, the sub categories for that category alone are expanded (AccesoriesExpanded.png).
When I click on the toggle button in the Category header, the sub-categories for all categories are expanded (AllCategoriesExpandedWithHeaderToggle.png). However the toggle buttons next to the individual category names (Accessories/Bikes/Clothing/Components) still show as collapsed. Is there a way to change the toggle sign on the individual category when an action is performed on the header.
I have attached pics of the toggle targets for individual category & category header (they are same basically) and a pic of the group explorer for better understanding.
The data source for the cross tab is
SELECT P.Name AS Product, PC.Name AS Category, PSC.Name AS SubCategory, SUM(S.OrderQty) AS OrderQty, SUM(S.LineTotal) AS LineTotal
FROM Sales.SalesOrderDetail AS S INNER JOIN
Production.Product AS P ON S.ProductID = P.ProductID INNER JOIN
Production.ProductSubcategory PSC ON P.ProductSubcategoryID = PSC.ProductSubcategoryID INNER JOIN
Production.ProductCategory AS PC ON PC.ProductCategoryID = PSC.ProductCategoryID
GROUP BY P.Name, PC.Name, PSC.Name
ORDER BY Category, SubCategory, Product
I hope this is brings more clarity and you are able to understand the problem. Please let me know if you need any more details.
Thank you
If there are two items targeting the same group, when you change the visibility of the group, the reporting engine automatically updates the controlling items and their state.
To avoid the issue you can remove targets which will be controlled by other targets, and set their initial visibility accordingly.
I hope this helps.
Regards,
Stef
Telerik by Progress
Rank 1
Hi Stef,
"If there are two items targeting the same group, when you change the visibility of the group, the reporting engine automatically updates the controlling items and their state." - This is exactly what I want, when the visibility of the group is changed by the header toggle button, the toggle buttons in the child items (targeting the same group) should change state as well. However this does not happen as you can see from the pics attached in the previous post.
I don't have any targets controlled by other targets, just two items controlling the same group - one at header level which expands the group for all parent rows and other at row level which expands the group for just that row. Hope this is clear. Thank you.
Please check the attached demo report in the Standalone Report Designer of R2 2017 to verify the settings are as yours. The TextBox in the header manages to expand all rows, but the Categorygroup's TextBox items do not have their actions' states updated.
Since the TextBox in the header is in the scope of the whole Table item and each TextBox item in the categoryGroup represents only the current group, I need to check if this behavior is expected or developer will change it.
For the time being, you can start the view with all groups expanded and all marks showing the '-' sign.
Regards,
Stef
Telerik by Progress
The issue is logged for improvement in our system. Please consider using only the group's Textbox item to control the visibility of rows due to the improper synchronization between actions.
Your Telerik points are updated to thank you for bringing the issue to our attention.
Regards,
Stef
Telerik by Progress
Rank 1
Hi Stef,
Thank you for confirming this. Yes, my settings are the same as in your demo report. I just wanted to make sure I wasn't doing anything wrong on my end.
Will this issue be resolved in the next release?
Thank you.
There is no ETA for the fix. Unless there is something more serious requiring more development and test time, the fix should be available until R3 2017 (in the middle of September, 2017).
Please follow the release notes to check if the fix is available or ping us through this forum thread.
Regards,
Stef
Telerik by Progress