Big Dynalist fan, for months now, and I’ve widely evangelized it, but this may be the hill my usage dies on, alas … It’s a veritable bug that links to an item aren’t preserved when the referenced item gets moved to another document. This all but shocked me. Links are a sort of data we log – data that quietly gets lost when we relocate an item, such that there’s no way to tell what we linked to originally, because what actually happened (infinitely less usefully) is that we linked to its page.
This isn’t just a feature limitation; it’s experienced as an actual bug (lost data), given how linking functionality is presented / commonly understood, and unexpectedly destructive; in good conscience, it seems to me an asterisk is required when people encounter Dynalist’s linking for the first time, so that they don’t discover this limitation along the way, after deploying too many links that end up obliterated from item migration. Am I missing something here?
The ideal for my purposes (as someone who moves items around a lot, and who would rather they remain where created but also appear in other docs) is to offer something like Trello’s forthcoming “mirror cards,” allowing items to live in multiple specified places. This would not only keep me on Dynalist but push me happily to paid.
Any chance, @Erica?
Every tool has its UX nits, but this is the core shortcoming of Dynalist and it has me seriously considering leaving, with a heavy heart, because I’ve invested so much here. Linking, even as a sub-optimal workaround method I use to try having items “bilocate” (or “tri-locate”) is largely a broken feature. Can you advise on whether you see it this way, or if I’m overlooking a better way to do this? Thank you, Erica!