Send Email via Outlook Data Source Action - HTML issues

  • 2
  • Question
  • Updated 10 months ago
  • In Progress
I'm setting up Outlook as a Data Source so that users can send emails from Skuid (which....by the way is very very cool).

All is connected and emails are sending fine. The issue I'm having is that text contained in a salesforce 'long text' field does not maintain its formatting, particularly for '/' forward slash characters.

The field value in the long text field looks like this:



However the email body in the email sent from outlook looks like this:




I have tried every combination I can think of:
- Rich text field instead of long text
- HTML email instead of plain text
- Triple braces instead of double braces on the merge syntax

and every combination of the ones above.

What am I missing here to make 'special' characters be correctly formatted?
Photo of Greg Jarrett

Greg Jarrett

  • 3,496 Points 3k badge 2x thumb

Posted 11 months ago

  • 2
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,056 Points 20k badge 2x thumb
Are you using Skuid Platform or Salesforce Skuid?
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,056 Points 20k badge 2x thumb
If you're on Salesforce Skuid, what version are you on?
Photo of Greg Jarrett

Greg Jarrett

  • 3,496 Points 3k badge 2x thumb
Salesforce Skuid. Millau 11.0.3 in a Sandbox
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,056 Points 20k badge 2x thumb
Can you post a screenshot of your "Send Email" Data Source Action? 
(Edited)
Photo of Greg Jarrett

Greg Jarrett

  • 3,496 Points 3k badge 2x thumb
Triple braces solve the line break issue, but not the date formatting. So "12/01/2018" gets distorted but all other text works just fine.
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,056 Points 20k badge 2x thumb
Just to verify, if you hard-code in the value, it works fine, right? It's only when you use the merge syntax that it gets garbled, right?
Photo of Greg Jarrett

Greg Jarrett

  • 3,496 Points 3k badge 2x thumb
Well this is odd, if I put a different merge field (with double braces) before the long text field (which contains a date), then it works fine, but if I put the long text first, the date gets gets garbled.

I also tried just entering some text before the merge field, but that doesn't work. Only entering another field with double braces merge syntax. Hard coding the date values also works fine.

Its like the first merge field activates something that then makes the long text field merge correctly after it.....