Add an option to export node links (e.g for Dynalist → Obsidian export)

Sorry, maybe I’m dumb, but I haven’t found neither a way to do this in the interface nor a corresponding feature request.

Imagine I want to export my Dynalist lists to Obsidian. I have a following doc:

The export options are as follows:

test doc
    node 1 [node 2](https://dynalist.io/d/NhzZarnud2k_xfC4cQOociTC#z=HssPCW7PawD2aN-C7V83jGv5)
    node 2
<body>
    <outline text="test doc">
      <outline text="node 1 [node 2](https://dynalist.io/d/NhzZarnud2k_xfC4cQOociTC#z=HssPCW7PawD2aN-C7V83jGv5)"/>
      <outline text="node 2"/>
    </outline>
  </body>

There is an internal Dynalist link, but it’s only for the node that is the target of a link. If I wanted to convert the exported file to individual markdown notes, it would be impossible since the original node id’s aren’t listed. Something like this could be helpful:

 <body>
    <outline text="test doc" node_id="NhzZarnud2k_xfC4cQOociTC">
      <outline text="node 1 [node 2](https://dynalist.io/d/NhzZarnud2k_xfC4cQOociTC#z=HssPCW7PawD2aN-C7V83jGv5)" node_id="NhzZarnud2k_xfC4cQOociTC#fxtDbXdmCVxYBsXtgJKK5TT2"/>
      <outline text="node 2" node_id="NhzZarnud2k_xfC4cQOociTC#HssPCW7PawD2aN-C7V83jGv5"/>
    </outline>
  </body>

That way one could easily write a converter to conveniently export all Dynalist data, keeping the internal links intact.

4 Likes

This is why I shun internal links in Dynalist and use tags and search instead.

This has come up in another thread related to HTML export. I’m surprised this isn’t a higher priority for development. There is a very simple fix, as suggested above by OP @Alexander_Peczony

It doesn’t seem very simple or like it would be high priority, since they said it would still need someone to write a converter. Or is node_id= valid code for anything? Locally hosted HTML doesn’t support file://#… internal links due to browser security. I’m not very familiar with Obsidian. Is that obsidian code in their example?