Create a parent note in-place for an existing tree using script?

[1ridic]

Hi guys,

I’m trying to create a parent node in place for an existing tree using a custom widget button. My current code is as follows:

api.addButtonToToolbar({
    title: 'New CTDP Node',
    icon: 'list-plus',
    shortcut: 'alt+n',
    action: async () => {
        const taskNoteId = await api.runAsyncOnBackendWithManualTransactionHandling(async () => {
            const CTDPRootNote = await api.getNoteWithLabel('CTDPRoot');
            const CurrentTree = await CTDPRootNote.getChildNotes();
            let newTitle = `#`;
            if (CurrentTree.length === 1 &&
                /^#\d+$/.test(CurrentTree[0].title)) {
                const num = parseInt(CurrentTree[0].title.substring(1), 10);
            newTitle = `#${num + 1}`;
            }
            const {note} = await api.createTextNote(CTDPRootNote.noteId, newTitle, '');

            for (const child of CurrentTree) {
                // await child.cloneTo(note.noteId)
                // await child.deleteNote()
                await api.ensureNoteIsPresentInParent(child.noteId, note.noteId)
                await api.ensureNoteIsAbsentFromParent(child.noteId, CTDPRootNote.noteId)
            }
            return note.noteId;
        });

        await api.activateNewNote(taskNoteId);
    }
});

However, when I click the widget multiple time, the tree appears as if the notes exist in both the new and old positions:

But after I refresh the frontend, the tree displays as expected:

My question:
Is this operation not supported yet or is there something missing/wrong in my code to properly update the frontend？

[dosubot[bot]]

Hi @1ridic! I'm Dosu and I’m helping the Trilium team.

This is a known UI artifact in TriliumNext: after moving notes programmatically, the frontend tree may not update immediately, causing notes to appear in both old and new positions until you refresh or re-select the parent. The backend data is correct; it's just a frontend update issue see details.

To fix this in your script, you should trigger a frontend event to force the tree to refresh after you move the notes. You can do this by emitting a treeChanged event or using frontend hooks/services like reloadNotesTreeView or NotesTreeService. For example, after your backend transaction, you can add:

window.dispatchEvent(new Event('treeChanged'));
// or, if available in your context:
api.emit('treeChanged');

This will prompt the UI to update immediately and reflect the new tree structure without needing a manual refresh. This approach is supported by recent frontend improvements in Trilium's event handling see PR #6731.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[1ridic]

Hi Dosu, I tried your solution but it did not work.

[dosubot[bot]]

The frontend tree not updating immediately after your script runs is a known UI artifact in TriliumNext, especially when moving notes programmatically—backend data is correct, but the UI doesn't always refresh until you manually reload or re-select the parent note see details.

Emitting a treeChanged event (via window.dispatchEvent or api.emit) only works if the frontend is actively listening for that event in your widget's context, which isn't always the case for custom scripts. Direct access to frontend services like NotesTreeService or reloadNotesTreeView is not exposed to custom widgets, so programmatic tree refreshes may not be possible without a full page reload or navigating away and back to the parent note see wiki.

Recent frontend changes (PR #6731) improved event handling, but unless your widget is running in a context where those events are registered, the UI won't update immediately. This limitation is confirmed in documentation and threads—no alternative method for forcing a tree refresh from custom widgets is currently documented.

If you want to troubleshoot further, check for any errors in the browser console when you try to trigger the refresh, and let me know your TriliumNext version—there may be version-specific workarounds. Otherwise, manual refresh or navigation remains the most reliable workaround for now.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[eliandoran]

@1ridic , it appears to be a bug in the note tree refresh, most likely due to the fact that there are many operations that might come out of order (deleting a branch, creating a new one).

[eliandoran]

To be treated as a bug in #6845.