I really like the search functionality: I could search for a keyword and it would instantly pull up a long list of results: all the places where the keyword was found, with surrounding context: very useful. I’ve just spent a fair amount of time converting a lot of the important keywords in my Rich …

I guess the thing is, before conversion, you had three examples of kibana, in different places (which may or may not be/mean the same ‘thing’) whereas after conversion, you have a single kibana, which happens to be referenced in 3 places. If the search worked as you would like it to, I could imagin…

I take your point, but in that case I may be using references wrong (and have spent about 8 hours over the weekend destroying information in my Rich Text fields!). I’ve been using references as “magic” replacements for existing entities: so for example a Task’s Details field might have contained: ……

Thanks very much! I’m going to assume for now that it’s going to be approved, and so I’ll continue incorporating Tags (References) in my Tasks’ Details. Is there a visible process for approving feature requests, so that I can watch for this feature getting into the roadmap?

I do have an immediate problem: having converted all my Tasks’ Details (Rich Text) fields by replacing plain text entities (“Kibana”) with References ([T] Kibana) I’m finding it much more difficult to keep track of progress: I was relying on search very heavily, and now I’m having to remember which …

(Replying to myself!) After seeing your very useful Reference scripting example in (How) can I display References in my Board and Feed views? I’m wondering: could I use a script to process the Rich Text contents of my Task’s Details field (whenever it changes) in order to reproduce it with all Refe…

Extracting useful info from Rich Text fields is harder than extracting info from References I’m afraid. The contents can be accessed via API as markdown, html or json, but I’m not aware of an easy way to parse it I’m afraid. Maybe some smart community member will figure something out :wink:

If it’s accessible as a JSON string then I can trivially convert into a hierarchy of dicts and arrays in javascript if I have access to JSON.parse(). Given that, then, would the JSON give me access to the name of the Referenced entity?

BTW I also discovered that I can link a word (eg. “Kibana”) to an Entity in a different way (via the popup toolbar in the Rich Text field): that highlights the word in a colored box and when clicked on it generates a floating popup containing the actual Reference: and that (highlighted, linked) word…

I’m afraid I’m not doing very well getting my test script to work (just trying to verbatim copy from (Rich Text field) Details to (Rich Text field) Details2 for now): const fibery = context.getService('fibery'); for (const entity of args.currentEntities) { const details = entity['Details'] …

This code will get the contents of the Description (rich text) field and put it in the simpler text field as JSON: const fibery = context.getService('fibery'); for (const entity of args.currentEntities) { const x = await fibery.getEntityById(entity.type, entity.id, ['Description']); const c…

After converting keywords to References, search for keywords is much less useful

Get Help

Topic		Replies	Views
Trigger on doc changes not working Get Help automations	23	670	April 15, 2023
References reloaded Ideas & Features	77	2918	September 24, 2024
Show in Reference Highlights Referenced Entity more clearly Ideas & Features blocks	15	1491	July 14, 2026
Allow Rules/Formula Involving Rich-Text Fields Ideas & Features formulas , rich-text	25	3653	December 12, 2024
The future of References: thoughts, questions, and ideas Second Brain for Teams	9	902	October 11, 2022

After converting keywords to References, search for keywords is much less useful

Related topics