Hi Dojo,
I have big table and I want to show some of the data like a table.
For better understanding I have a picture here of one row and only 2 brands (there are more than 10 brands):
Children I have configured like this, selecting the row is working fine:
Displaying here the data for Canal+ AT:
But my issue is to show all brands when there is a yes in the first column. In my example for pid 115 and 116. Because if I copy the three fields here and adjust it for pid 116 it will not be displayed, I guess because of only one row will be displayed.
Hi Toon,
the data is coming from a database and stored here in one element.
In the first picture I added the PIDs.
But I will write it here because it's hard to read:
115 Canal+AT (YES/NO)
200 Canal+AT Brand
201 Canal+AT Replay
202 Canal+AT Restart
116 Telesat (YES/NO)
210 Telesat Brand
211 Telesat Replay
212 Telesat Restart
Basically the parameters is saying if the other 3 parameters are shown or not. Of course I could show with hardcoded shapes but than I will have gaps. Therefore I was trying to find a solution with children row.
So either 115 or 116 will be yes, not both? And you want to show specific parameters based on that? Am I getting that right?
Almost, because they can be both yes or both no, but indeed when one is yes 3 parameters should be shown.
But I have only shown 2 brands in fact it's much more.
So in case both are yes, what do you expect then? 6 blocks visualized?
Given the complexity of the use case, I would personally suggest moving into a low code app solution. I currently also don't see a way to properly do this in Visual Overview as you would need to dynamically position the contents of your row template so that it collapses your brands when needed.
In Low-Code-Apps, however, you can leverage the Grid visualization and its html templating. With html, you get full access to css as well, which means you can use things like "display:none;" to collapse parts of your row. It's not the easiest thing to implement, but some experience in both LCA and html/css should allow you to do this.
Hi Stefan, would it be possible to rephrase that last paragraph? I'm afraid I'm not entirely following where the 116 comes from.
As a sidenote: if this is a child row that subscribes on data from other tables, we nowadays recommend using table joins in LCA, enabled by GQI. Making separate subscriptions for each row is less performant and thus not recommended anymore.