Autoresponder showing December 2018 date not December 2017

[mjokiman]

Hi, one of our donors let us know that the autoresponder she's getting showing December 2108 date. I checked the template and this is the merge fields <@CnP_Transaction_Month_Text> <@CnP_Transaction_Day>, <@CnP_Transaction_Year> which looks right to me so i'm not sure why it's showing 2018 when the transaction date shows Dec 2017.
This is the transaction where the donor is getting the 2018 date:

Transaction: 36448-1712311808086205318
Total Amount: $150.00
Transaction Date: December 31, 2018

Thanks,
Monica

[CnP.Support]

Good day mjokiman

Sorry for the inconvenience. Please see this post: https://forums.clickandpledge.com/fo...ipt-date-error

We were notified of this last week and have been working with Salesforce support to determine the root cause.

[mjokiman]

Thank you for the quick response. Has this issue been escalated with Salesforce? (was wondering if I should push this issue with Salesforce as well to help move it along quicker?)

[CnP.Support]

Good day mjokiman

We have identified the problem and it is an unfortunate mistake on our part. The problem only shows itself in the first week of the year and the last week.

The formatting YYYY and yyyy are 2 different formats. YYYY stands for week year and yyyy stands for year. We have identified the issue with Salesforce. Hearing about "week year" was a new one for us as well. You may want to research it.. amazing how these things work.

We are working on a patch to release later this week. Currently we are testing it and will notify all clients once we have reviewed our entire code for all apps.

Sorry for the inconvenience.

[mjokiman]

Hi, has this issue been resolved?

Thanks

[CnP.Support]

Good day mjokiman

This issue is part of an update due out later this week. Salesforce apps will have an update scheduled for release this week, once all test are completed.

The date issue naturally does not affect anything now as it only is a problem the last week and the first week of the year. The fix will resolve it once your instance receives the update.

Hope that answers your question.