Skip to content

[Bug]: Bidirectional linking many-to-one not working #1080

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

Open
2 tasks done
ac8318740 opened this issue Oct 22, 2024 · 0 comments
Open
2 tasks done

[Bug]: Bidirectional linking many-to-one not working #1080

ac8318740 opened this issue Oct 22, 2024 · 0 comments
Assignees
Labels
bug Something isn't working triage Issue not tagged yet. talking to the user

Comments

@ac8318740
Copy link

Contact Details

alexcoote@outlook.com

What happened?

When setting up bidirectional linking, many-to-one relationships don't work.

I have a field with ID "relation" set up on 2 tables. Table one is objects that should feed into higher level objects on table two. Think segments to companies.

I want the relation field in table two to include all the segments that are tagged to that company. The tagging is done with the relation field in table one.

However, it doesn't work.

  • When I have company A tagged once across all rows in table one, the output in Company A YAML is something like this:
    • Relation: "[[!AutoStorage/Database Files/01_Financial Metrics/18b1ff4e-5021-451b-83a0-ba6700778002.md|18b1ff4e-5021-451b-83a0-ba6700778002]]"
  • When I have company A tagged twice across all rows in table one, the output in Company A YAML is something like this:
    • Relation: "[[!AutoStorage/Database Files/01_Financial Metrics/18b1ff4e-5021-451b-83a0-ba6700778002.md|18b1ff4e-5021-451b-83a0-ba6700778002]], [[!AutoStorage/Database Files/01_Financial Metrics/17bf0398-a15e-450b-83d7-64890c2fa3b9.md|17bf0398-a15e-450b-83d7-64890c2fa3b9]]"
    • This type of output doesn't show up in the table. If I reformat as per the below (i.e., a list format), it does. I believe if we could reformat the output to a list type then I could get a formula rollup to work
    • Relation:
      • "[[!AutoStorage/Database Files/01_Financial Metrics/18b1ff4e-5021-451b-83a0-ba6700778002.md|18b1ff4e-5021-451b-83a0-ba6700778002]]"
      • "[[!AutoStorage/Database Files/01_Financial Metrics/17bf0398-a15e-450b-83d7-64890c2fa3b9.md|17bf0398-a15e-450b-83d7-64890c2fa3b9]]"
  • Further to this issue, whenever any of the Company A relation values are removed in table one, all of them are deleted from the relation property in the Company A file (I believe because code is seeing delete then deleting all given they're just one long text string)

All of this works fine if I do it from the one-to-many side (i.e., update the relation field in table two). In this case, it is formatted as a list automatically. However, this is impractical for my use case as I need to be able to relate segments back to their company parents when creating them.

What platform were you using?

Desktop

Version of the plugin

3.5.1

Relevant log output

No response

Are you using the latest version of the plugin in your Obsidian vault?

  • I have verified that I am on the latest version

Are you check if there is a similar issue?

  • I have verified that there are not similar issues
@ac8318740 ac8318740 added bug Something isn't working triage Issue not tagged yet. talking to the user labels Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Issue not tagged yet. talking to the user
Projects
None yet
Development

No branches or pull requests

2 participants