I am working in my record type display interface.
One of the fields in our data contains an email address with the name of the person in this format:
Bilbo Baggins <Bilbo.Baggins@TheShire.org>
I need to extract the string between the < > and display that string as a mailto link in my results.
How do I write this, or if it's not possible to write this, how can this be achieved based on the data as it is?
Many thanks in advance -
Discussion posts and replies are publicly visible
a!richTextDisplayField( value: a!richTextItem( text: extract("Bilbo Baggins <Bilbo.Baggins@TheShire.org>", " ", "<"), link: a!safeLink( uri: "mailto:" & extract("Bilbo Baggins <Bilbo.Baggins@TheShire.org>", "<", ">") ) ) )
> extract("Bilbo Baggins <Bilbo.Baggins@TheShire.org>", " ", "<"),
By my math, that would evaluate to a text value of "Baggins " - is that the intent?
(i guess it doubles it based on the fact that there are 2 copies of the "start delimiter" i.e. a blank space)
do you still get that error if you add the (required) ":" after "mailto"?
ed: i don't get the error in my CE site...
Yes, I caught that typo and fixed it, but still receive that error message. Strangley though it didn't give me the error when it was first implemented...
a!safeLink [line 81]: mailto: is not a permitted URI under the configured security rules and cannot be cast to safeUri.
Works in my CE site (and in the shared beta site). If you just make a new unsaved interface with this code do you still get the same error?
mailto: -- needed to be mailto://
All set! Thank you!
weird, it actually works for me when i try it either way.
Scott Fleming said:needed to be mailto://
According to this
https://www.w3docs.com/snippets/html/how-to-create-mailto-links.html
there are no "//" in a valid mailto link.
Stefan Helzle said:there are no "//" in a valid mailto link
maybe his environment has some setting which disables regular mailto links via some heuristic, and adding the "//" accidentally defeats it?
that's why i was trying to see whether the generic code pasted into a blank interface would produce the same issue...
yeah, i got the same result (posted earlier), so who knows i guess? it'd be interesting if there was some issue being caused by trying to use it in the record list configuration (though i don't know why it would do that).