Forum Discussion
MattMelrose
4 years agoQrew Member
Yup! that is exactly what I am trying to do.
------------------------------
Matt Melrose
------------------------------
------------------------------
Matt Melrose
------------------------------
MarkShnier__You
Qrew Legend
4 years agoYou can use a URL Formula to pre-populate many fields in your email message in addition to the recipient, such as the CC, BCC, Subject, and message body, like this:
"mailto:"
& [To:] // email field to email to an this could contain, a semi colon delimited string.
& "?cc=" & [CC] // optional CC //note that the ? delimiter only gets used once, right after the TO.
& "&bcc=" & [BCC] //optional bcc
& "&subject=" & URLEncode([Subject]) // optional Subject
& "&body=" & URLEncode([Body] // optional body
note that you are constructing a URL, which needs to travel the vagaries of the internet and URLs do not allow any special characters or blanks. So any fields which might contain illegal characters need to be URLEncoded. The email recipients can be semi colon delisted.
to get a carriage return you would use
\n
but that would need to be URLEncoded.
like
& URLEncode ("\n\n")
to start a new paragraph.
As far as I know, this is the only syntax which will work on all email clients (so say gmail and Outlook and the rest). It will NOT allow any fancy Rich Text ( like bold or font control), just plain text.
Give it a try and post back if you get stuck. The symptom of not URLEncoding will be that the page load into the email client will stop at the first illegal character.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
"mailto:"
& [To:] // email field to email to an this could contain, a semi colon delimited string.
& "?cc=" & [CC] // optional CC //note that the ? delimiter only gets used once, right after the TO.
& "&bcc=" & [BCC] //optional bcc
& "&subject=" & URLEncode([Subject]) // optional Subject
& "&body=" & URLEncode([Body] // optional body
note that you are constructing a URL, which needs to travel the vagaries of the internet and URLs do not allow any special characters or blanks. So any fields which might contain illegal characters need to be URLEncoded. The email recipients can be semi colon delisted.
to get a carriage return you would use
\n
but that would need to be URLEncoded.
like
& URLEncode ("\n\n")
to start a new paragraph.
As far as I know, this is the only syntax which will work on all email clients (so say gmail and Outlook and the rest). It will NOT allow any fancy Rich Text ( like bold or font control), just plain text.
Give it a try and post back if you get stuck. The symptom of not URLEncoding will be that the page load into the email client will stop at the first illegal character.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- MattMelrose4 years agoQrew Member
Wonderful, appreciate you help, works flawlessly