Move away from inline keys

What I’m trying to do

Is there a different solution to using inline keys and still getting the benefits of a nicely formatted Dataview table showing the contents of the line after a specific inline key?

I have thousands of notes that have inline keys. I love how this allows me to use Dataview queries to see the full context of a link in a note. But, my mobile app is really slow and I keep seeing people discouraging use of inline keys. It seems Datacore also discourages inline keys.

Things I have tried

I’ve converted every inline key to properties that makes sense.
A few of my inline keys contain line/block/paragraph of content that I want included in the body of the note and in the context of other lines/blocks/paragraphs. For example, I have brief comments on interactions with people (this is my personal CRM). In that person’s note, I have a query that shows all of my interactions. I don’t need to sift through backlinks. It’s nicely sorted & formatted in the Dataview table.
I don’t prefer showing backlinks in the note - that doesn’t provide the sorted, clean view of a Dataview table. Unless I’m missing something, embedding search queries is similar to showing backlinks in the note.

Both backlinks and embedded search can be made to look cleaner with a CSS snippet like Improving embed queries integration or Smoother looking embedded search (CSS snippet).

1 Like

That’s essentially what I’m trying to achieve too but I want a way that is both supported and easy to use. Did you find anything?

Not really. I just resigned myself to the fact that dataview queries are the best solution for what I’m trying to do in my vault - until something changes. I have found it helpful to try where I can to limit my use of them by using Bases where possible. And in a lot of notes, I’ve tried to simplify by combining two queries into one or delete some unneeded queries. After a little bit of time doing this, I’ve noticed my startup time on iOS has gotten incrementally snappier.

1 Like