M2A relationship is not displayed correctly

[Abdallah-Awwad]

Thanks @smartlabsAT for this great extension and your continuous work on improving it.

I ran into a non-blocking issue and wanted to report it in case it helps future improvements.

One of my collections uses a Many-to-Any (M2A) relationship, but it doesn’t seem to be supported correctly by the extension at the moment.

I also tried adding a custom template for that field, but that caused the layout to break and it shows 0 results instead.

It would be great if M2A relationships could be supported in a future release. 🙏

Thanks again for your work!

[smartlabsAT]

Hi @Abdallah-Awwad, thanks a lot for the detailed report and the screenshots — they made this easy to reproduce and pin down. 🙏

Many-to-Any (M2A) fields are now supported and this is released in v0.5.0.

What was fixed and added:

• M2A now renders in the table via the related-values display or a per-column template using the {{item:<collection>.<field>}} syntax — including nested chains like {{item:partners_catalog.catalog_id.title}}. Each junction row resolves against its own target collection.
• The "0 results" / blank table when adding a Column Display on an M2A field is fixed — invalid token paths are no longer sent to the API, so it can't 403 anymore.
• Permission-aware: if you can't read a target collection, that row shows a block icon instead of breaking the table; you still see the collections you can read.
• The Column Display editor now shows a hint with the allowed collections and the correct token syntax for M2A fields.

You can grab it here: https://github.com/smartlabsAT/directus-super-table/releases/tag/v0.5.0

One note: inline editing of relational fields (M2O/O2M/M2M/M2A) is intentionally out of scope here — relational fields stay display-only for now. That's tracked separately in #61.

If you run into any remaining issues, please open a new issue with your field/collection setup and we'll take a look. Thanks again! 🚀

[Abdallah-Awwad]

Thanks, @smartlabsAT, for the quick action. I really appreciate it. The customized tip you added and the attention to detail are especially impressive.

Unfortunately, I’m still unable to get it working. I recorded a short video to demonstrate the issue, hopefully it helps clarify what I might be missing:

Super-Table-M2a-22.mp4

One note: inline editing of relational fields (M2O/O2M/M2M/M2A) is intentionally out of scope here — relational fields stay display-only for now. That's tracked separately in #61.

That makes sense. I can see how complex that feature would be to implement.

[smartlabsAT]

Hi @Abdallah-Awwad,

Thanks a lot for the quick follow-up — and especially for the video. That made it easy to see exactly what was going wrong. 🙏

The video showed the piece we'd missed: when you build the column display with the native field picker, it emits tokens prefixed with the field name (e.g. {{treatment.collection}} and {{treatment.item:<collection>.<field>}}), whereas v0.5.0 only understood the hand-written {{item:...}} form — so the cell stayed empty. That's fixed now, plus a couple of related improvements:

• Templates built straight from the picker render correctly.
• Discriminator-only templates (e.g. {{collection}}) no longer blank the cell.
• You can also mix in parent-row fields (e.g. {{code}}) and junction-level fields.

This is released in v0.5.1: https://github.com/smartlabsAT/directus-super-table/releases/tag/v0.5.1

Could you give it a try when you get a chance? If anything is still off, please share the details here — your M2A field setup (the field and its allowed collections) and the exact template you're using — and we'll dig in right away.

Thanks again for the detailed reports!