Scrolls appear and I need to synchronize them in all tables. Because the table header is only in table 1.
Do you have any idea how this can be done?
Or maybe we should use a different data output structure? I tried to make a common table, but then I can't synchronize the common information for each article.
Hi @incolor09, if I understand your use case correctly this looks like a good fit for a Table with grouped rows, which would replace the List View containing table2. That would allow all of the articles to share the same column configuration.
However, I don't believe there is a way to synchronize the column configuration for the content in table1 and table2 otherwise. We would need to consider that as a feature request.
Let me know if the grouped rows feature helps here. For the general column synchronization feature request, it would be helpful to get more context on your use case. I can't read the text so I'm not totally sure I understand what table1 is being used for. Thanks!
Hello, jacobstern. Initially, I tried using a table with grouped rows, but then I can't use the info section, which displays detailed information on each of the articles (photo, article, price, etc.).
Maybe there is a solution how to add this info section when opening the grouping string? That would solve the problem.
I think I can combine the information from table2 and table1 into a common table.
table2 shows the detailed data for each item (orders, sales, advertising expenses, etc.). table1 shows the sum of some items from table2 (orders, sales, and advertising expenses)
Right, I see what you mean. Well my recommendation at this point would be to see if you can use the table columns across the different parts of the UI, since it seems like without the dynamic columns you're pretty much covered here. Unfortunately I don't think there will be a way to fully replicate the screenshot with grouped rows (that is, including the "info" section).
After your back and forth with @jacobstern, it certainly seems there isn't a native solution that will give you the desired layout and behavior for a larger number of columns. I think a table with grouped rows is probably your best option, though. I'll talk to the team about potentially adding a single "summary" cell or similar that would allow you to implement your desired info section.
I think a table with grouped rows is probably your best option, though. I'll talk to the team about potentially adding a single "summary" cell or similar that would allow you to implement your desired