Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for "corresponding field" seems to be missing #12146

Closed
3 tasks done
thepurpleblob opened this issue Mar 14, 2022 · 0 comments
Closed
3 tasks done

Documentation for "corresponding field" seems to be missing #12146

thepurpleblob opened this issue Mar 14, 2022 · 0 comments

Comments

@thepurpleblob
Copy link

Preflight Checklist

Describe the Bug

See https://docs.directus.io/configuration/relationships/

A few lines down the docs say...

"You also have the option to create a Corresponding Field during this process. This allows you to more easily create the O2M alias (see below) that pairs with this M2O"

However, the next time it's mentioned...

"You also have the option to create a Corresponding Field during this process. This allows you to more easily create the M2O field (see above) that pairs with this O2M."

Notice see below / see above. I can't see that it's actually documented anywhere

It sounds like an interesting feature but I don't really know what it does or how to set it up.

To Reproduce

n/a

Errors Shown

n/a

What version of Directus are you using?

9.6.0

What version of Node.js are you using?

n/a

What database are you using?

SQLite

What browser are you using?

Chrome

What operating system are you using?

Ubuntu

How are you deploying Directus?

Docker

@thepurpleblob thepurpleblob changed the title Documentation for "corresponding field seems to be missing" Documentation for "corresponding field" seems to be missing Mar 14, 2022
@directus directus locked and limited conversation to collaborators Mar 15, 2022
@rijkvanzanten rijkvanzanten converted this issue into discussion #12176 Mar 15, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant