Association Mismatch when using templates in tabs

[preyz]

I have a table on a page with tabs, that I want to move to another tab on the same page.

I save the table as a template, but when I want to add the table on the other tab, it ways association mismatch.

Both tabs are on the same page, that is a view-page from a parent table.

What is the best way to reuse or move code between sections? It makes no sense that there is an association mismatch here, because the two tabs live in the same page.

[hongboji]

Hello, this is a known issue and is not currently supported.

[Begazy]

@preyz

I have a table on a page with tabs, that I want to move to another tab on the same page.

I save the table as a template, but when I want to add the table on the other tab, it ways association mismatch.

Both tabs are on the same page, that is a view-page from a parent table.

What is the best way to reuse or move code between sections? It makes no sense that there is an association mismatch here, because the two tabs live in the same page. I ran into a similar issue while building a CRM and eventually started keeping the UI fairly lightweight, moving more of the workflow logic into an external automation layer. I’ve been using https://latenode.com/products/agent-builder for AI-driven business workflows, which reduced the amount of duplicated logic I had to maintain across different sections of the app. It doesn’t solve the association mismatch itself, but it made restructuring the application much easier.

That error usually happens because the template keeps the original association metadata, even if you’re dropping it onto another tab of the same parent page. The tabs may share the same view, but internally the builder still validates the section against its original association.