Date fields not working in autoresponder letter template

[CnP.Support]

Good day!

Please note that you have defined variables that are not ours - {!TODAY} is not one of our parameters and as such we do not replace it in run-time.

It is also important to note that TESTS of autoresponder do not have these values as no transaction is being referenced.

[wtben]

Thanks! I just updated.

[CnP.Support]

Good day!

No- it is a free service and we will upgrade you in 24 hours. Please see that support ends for versions that are 2 releases behind. See our release notes:

- http://manual.clickandpledge.com/Sal...ase-Notes.html

Support for your version ended in April 2015.

We ask that you stay up-to-date and we do it all for you.. just ask & grant us access. We will do the rest.

Let us know if we can be of any help.

[wtben]

Are there any risks to or prerequisites for doing so?

[CnP.Support]

Good day!

Your instance is not at the latest. See below:




Before we can move forward we have to upgrade to release 9.2. Is it OK to upgrade you?

[wtben]

I created custom Transaction field with a formula field for today's date in the form I want. I was immediately able to select this merge field from the list. However, it does not display translated.

[wtben]

In testing our autoresponder, we're finding that none of the date fields are working in our letter template. The three fields we're currently using are:

1. {!TODAY}
2. {CnP_PaaS__CnP_Transaction__c.CnP_PaaS__Charge_Dat e__c}
3. {CnP_PaaS__CnP_Transaction__c.CnP_PaaS__Transactio nTimeZone__c}

We still wish there was a better field for "today's date" that could be formatted as desired, such as "October 28, 2015" instead of the informal "10/28/2015" that the TODAY formula reveals. In the meantime, though, resolving the failure of these fields is the more immediate priority.