Hi everyone, I need some help with bulk hyperlinking in Glide.
I’m trying to automatically hyperlink certain keywords or tags throughout my app. Ideally, whenever a specific word appears (like an acupuncture point name), it would become a clickable link that opens an image stored online (e.g., Google Drive or a direct image URL).
Is there a way to do this in bulk rather than manually creating each hyperlink one by one? I have too many to handle individually. Any suggestions would be much appreciated!
You could probably create a template column that takes the text as input, and then create replacements with html to for each link. Then display the result in a rich text component.
Thank you Jeff. I was hoping to have those words linked to images so i can click and view the photos. I see the hyperlink will have to open in a browser which would not be ideal if i wrap this up in app stores. Id prefer to have images opened within the app. Is that possible at all?
Got it. Only thought I have would be to do something with the custom AI component. Off the top of my head, I’m not sure how it would be structured, but you could have your text as one input. Maybe another input with JSON or something similar that would define a word and it’s associated URL. And an action that would show the image within the app.
One workaround is to store your keywords and image URLs in a separate table, then use relations to match the keyword in your text. Instead of hyperlinks, show those keywords as a list or chips when tapped, you can open a details screen with the image right inside the app. No browser needed.
Thanks for your suggestion about using a JSON-style keyword-to-image mapping to make acupuncture points clickable inside the Glide app.
After exploring the idea(if I understood you correctly), I ran into a core limitation within Glide’s relational logic:
Glide relations do not support matching multiple values from a single cell.**
For example, if I list acupoints in one cell like: BL32, TE5, GV20 — Glide cannot relate this to a Points table where each point exists as a separate row. The relation simply fails. The solution was to replace the comma-separated list with a junction table (aka many-to-many mapping) which is not ideal for what I wanted to build.
@Mazen , yes, I was thinking along the same lines. Am I correct that those keywords would need to be listed separately and individually, rather than being directly clickable within the main content tex?