Copilot email token formatting

  • 30 November 2015
  • 4 replies
  • 50 views

When using number and date field tokens in an email template, they are formatted the way they appear in the DB (from what I can tell) and do not show up in a way you would type them if a human had written the email personally.



In our example, we are sending a notification to customers that their renewal is coming up with the date of the renewal and the expected renewal cost.  However, the date field shows up as 2015-12-31 and the currency field shows up as 150000 (no $, no commas).  I can add the $ character, but I cannot add the comma.



I effectively will not be able to use copilot for this unless I can either a) have them formatted in the expected manner (12/31/2015 or Dec 31, 2015) or b) select from a few formatting options.  B would be better because then I could apply European formatting to those customers if desired. 31.12.2015 and $150.000,00 for example.

4 replies

Userlevel 5
Thanks Bradin for your feedback. We are working on improving the support for date formats and currencies. Will keep you posted on the ETA. However support for multiple formats based on the customer's location might not be possible in short term. 
Userlevel 5
This enhancement is underway and will be release by April first week. Support for international Date and number formatting is part of the enhancement.
Badge
Hi - There are formats available now, but I think there is a gap in the options available. There is no option for a standard number format (with commas) that doesn't also have a decimal. This is a significant gap as the only options to exclude the decimal is to use periods or spaces, which would be confusing for a standard number format.
Userlevel 1

@elizabeth_adams_c593ee I was able to work around this with a data design, you might be able to do this with a transform. 

 

With my data design, which I’m referencing in my query, I set up a Formula Field in my last transform that’s a ToString function. When I convert my number to a string in the data source, it doesn’t try to recast the data type when I use the token. For good measure I also load the variable into a string when configuring the additional fields.

Reply