Table sorting > Reusable component issue

[Sergey_Androsov]

Hi @Manuel_Germano
I revisited the issue, and unfortunately, the previously suggested workaround does not work as expected. While we had plans to introduce functionality for communication between data containers within reusable components and other data containers, it’s not currently a priority.

I’ve implemented a working solution in your application on the testTable3 page. Key points:

• I used the data container of the Reusable Component itself, not a block within it. This ensures proper data transfer into the Reusable component.
• Inside the component, I utilized Page Data to store the updated data after sorting.
• The Data Repeater logic now reads directly from Page Data, which is updated by the reusable component.

Please also check this related topic for additional context:

How can a reusable component access data model of its parent?

Update: found a workaround: we can a) enable data container for the reusable component, and then b) wire up the Data Model logic for the reusable component in the parent container, like so: [image] then everything is “repared” and works: [image]

Let me know if you need further clarification!

Regards,
Sergey