Skip to content
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

Interface not correctly configured in target collection for "One-to-Many" relationships #8315

Closed
3 tasks done
paescuj opened this issue Sep 25, 2021 · 0 comments · Fixed by #8317
Closed
3 tasks done
Assignees
Labels
Milestone

Comments

@paescuj
Copy link
Member

paescuj commented Sep 25, 2021

Preflight Checklist

Describe the Bug

When creating a "One-to-Many" relationship between two collections and choosing the "Create Field" option under "Corresponding Field", it seems like it's creating the field in the target collection with a wrong interface type:

Screenshot 2021-09-25 at 14-11-51 Messages

Edit:
Payload looks like this:

   "meta":{
      "interface":"many-to-one",
      "special":[
         "m2o"
      ]
   }

To Reproduce

  1. Create two collections (a & b)
  2. Create a "One to Many" field in collection a pointing to a field in b
  3. In the "Relationship" tab enable the option Add Many-to-One to "b"
  4. Open data model of collection b, edit the corresponding field and see the error message Interface "many-to-one" not found

What version of Directus are you using?

v9.0.0-rc.94

What version of Node.js are you using?

Docker Image

What database are you using?

Postgres 13

What browser are you using?

Firefox

What operating system are you using?

macOS

How are you deploying Directus?

Docker

@azrikahar azrikahar self-assigned this Sep 25, 2021
@rijkvanzanten rijkvanzanten added this to the v9.0.0-rc.95 milestone Sep 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants