A table in a matrix with the same handle as a table field overrides the schema for the field

[Tam]

Description

A table field that shares the same handle as a table field in a matrix will have it's type handle_TableRow overridden in the graph schema.

For example, if I have a table in a matrix field called answers and a top-level table field called answers, both will point to the same schema type of answers_TableRow. The properties of this schema will match only one of the types, meaning the values for the other will be incorrect.

Steps to reproduce

1. Create a table field
2. Create a matrix field containing a table of the same handle as the above but different columns
3. Try to query the data from both

Additional info

• Craft version: 3.7.35
• PHP version: 8.1.1
• Database driver & version: MySQL 5.5.5

[andris-sevcenko]

This is currently slated for Craft 5.0 as this is highly likely to break existing GraphQL queries.

[elivz]

Any update on this? I see it was removed from the 5.0 milestone. We just spent a bunch of time trying to debug why a nested field (SuperTables inside a Matrix, in our case) wasn't coming through in the schema before finally tracking it down to this issue. At the very least, it seems worth calling out in the GraphQL documentation, as sharing the same field handle across multiple Matrix blocks is very common in my experience, especially in a content-builder style setup.

[brandonkelly]

Yep, it’s already resolved for 5.0 actually :) Will update the issue once the solution is public.

[brandonkelly]

This is solved in Craft 5 because all fields are now defined globally, with unique handles.