Inline bases code

Help
1

First, search the help docs and this forum. Maybe your question has been answered! The debugging steps can help, too. Still stuck? Delete this line and proceed.

What I’m trying to do

Trying to figure out where certain information are stored.

Things I have tried

Asked AI and Google.

Obsidian Bases. A question of understanding. When I create a base inline (!) in a note and then add an attribute, such as “file path,” this new column remains intact but does not appear in my inline code. Where is it stored?

2

If you mean in a base embedded like ![[example.base]], then it’s in the .base file. You can open it with an external text editor or the (at least one that I’ve seen) plugin that lets you edit it in Obsidian.

If you mean in a base embedded like:

```base
```

then the info will appear right there in the code block.

This is the code for a, um, base base:

```base
views:
  - type: table
    name: View
    order:
      - file.name

```

This is the code after you add the file path column:

```base
views:
  - type: table
    name: View
    order:
      - file.name
      - file.path

```
3

Hello Dawni,
Thank you very much for your reply. Yes, I meant a code block that is inserted into the note. And something strange happened here. When I inserted the base code block in a “Callout” (using the “Callout Toggles” plugin), the properties in the base code were NOT added to the note but still worked. When I removed the Callout, the changes in the base disappeared and no longer worked. I have no idea why this is the case. Without a callout, everything works as you described.

4

Aahh, a code block base in a callout. Unfortunately,:

5

If the block base in a callout is being used for a dashboard or something and won’t be changing much, you could:

  1. set the base block up as you’d like (filters, properties shown, etc.)
  2. select it all
  3. run the Insert callout to wrap it up in a callout and never touch the controls.

You could probably get fancy with some css and a custom callout that hides the base block controls so you’re not tempted to touch them.

Embedding the base is also an option – those seem like you can (mostly) interact with them and the changes are saved back to the .base file.

> [!example] embedded base
> ![[Basebase.base]]