Bases formula property link function interpret "#^" as ">^"

Help
1

In bases, I have a formula property trying to generate a link to the note’s “abc” block

link(file.name + “#^abc”)

The resulted link comes out as
file.name >^abc

Any way to use original “#^” instead of intepret as “>^”.

1 Like
2

The “>” is how block links are rendered. If you paste this into a note:

[[example#^abc]]

… and switch to the Reading view, you’ll see the link rendered as example > ^abc . So I think the characters in your formula are rendering the way you would want them to.

To the crux of your question though, it seems that internal links from Bases formulas don’t include the href info needed to link to a block. Even if you hand your formula a complete link like this:

---
blockID: "[[example#^abc]]"
---

```base
formulas:
  this.blockID: this.blockID
views:
  - type: table
    name: Table
    filters:
      and:
        - file == this.file
    order:
      - formula.this.blockID
      - blockID

```

… the formula column this.blockID stills links to the whole note, not to the block. But the property column blockID does link to the block.

Unless someone has a workaround, it might be a current limitation of Bases that you can’t use a formula to create a link to a block.

hovering over first column (this.blockID)
hovering over first column (this.blockID)982×682 29 KB

hovering over second column (blockID)
hovering over second column (blockID)1000×643 27.4 KB

1 Like
3

thank you. This is exactly my problem as the rendered link pointing to the whole note, not the block. I thought it’s “>^” issue. Thanks for pointing it out and help!

Hongjun

1 Like
4

The same behavior also occurs with an internal link that points directly to a paragraph in a file.

For example: [[File#Paragraph]] - link(File + “#Paragraph”)

1 Like
5

I am trying to apply link(file.name+“#Status”,“status”) to empower me to mouseover the word status in my bases table and see the status of the file but instead I only get the top of the page which I could get from the link to the entire file already.
Having the link in a property works but forces me to manually edit all legacy pages.

Is there going to be support for this later? Is it a bug or a reduced functionality link that can benefit from a feature request?

1 Like
6

I have same problem.
If I navigate block/heading link from “default“ link property (embed, backlinks, filelinks), they all render as entire page link.
I think it’s because of indexing so not the bug, but the specification.