Why I need this feature ?
Bcz It’s more convenient that the first time organize knowledges with outline view. But after outline view done. it’s not enough , We have to handle data in Table view and without repeating input the same datas. Such as, filiter , formula, add Note, multi-selection, etc in Table View.
@Steve_Yang feel free to reuse my template, but your case is even simpler. You don’t need to combine subitems or preserve checkbox status or whatnot, I assume, so you can just .Split(Character(10)) your list and .FormulaMap(AddRow...)) then. You can still use parts of my template to determine list nesting level based on inner object structure, but no need to manipulate those back into text items.
This is a great first step! But the second step is key: How do you preserve parent-child relationships when converting the outline into the table? Can you “read” a bullet’s indentation level to identify its parent bullet? If so, how do you then feed the parent row into a second “Parent” column?
In other words, how do you get from the outline below to the table below?
I did this by examining the underlying structure of the rich text — e.g. here:
You can look into the free version doc that’s linked in that topic, HLP Initial tasks input table. It’s not the most optimal solution there but it may give you ideas.
If you implement this now though, be prepared to fix this sometime very soon. Coda is changing the way it stores text, so it won’t be the same structure to examine anymore. Not significantly different but it will require adjustment anyway.