Receipt Date Error

[CoralReefAlliance]

Hello,

We're currently having an error with our autoresponder receipt giving the incorrect year. Our timezone settings are correct, and we've tried both the Transaction and Send Date merge field. Do you have any insights on why this might be happening? Given that these receipts are used for tax purposes, it's crucial for us to be able to get the date correct.

Thank you for any feedback!

[CnP.Support]

Good day CoralReefAlliance

Please grant us Salesforce login access so we can review the account and let us know your Salesforce Organization ID.

What is your C&P account number?

[CnP.Support]

Good day CoralReefAlliance

I did a quick check to see if I can find your account and see the following:



Is this your account?

The instance is several versions behind. Please see the release notes:



Your instance is 4 versions behind..

The issue you are having must be related to the time zone differences or what you are using. Naturally the time zone appears to be many hours ahead. Once we have access we can determine the root cause. The C&P Account is set to the right time zone so this must be a Salesforce time zone issue.

[CoralReefAlliance]

Hello,

Thank you for your response on this holiday! Our org ID is 00D70000000Ilsw and access has been granted for 24 hours.

[CnP.Support]

Good day CoralReefAlliance

Sorry for the late reply- we waited for your response for a while but did not hear back. We were monitoring and handling posts till 6 p.m. ET.

While we are reviewing the issue, is it OK if we upgrade your instance? Your installation is several updates behind and is no longer supported.

[CnP.Support]

Good day CoralReefAlliance

We have reviewed the case and have submitted a support case with Salesforce. It is quite a strange case.

The date that is being posted is 2017 but Salesforce format changes it to 2018. The command we have in the Autoresponder is as simple YYYY format for the year - before the format we see the date as 2017 but once Salesforce formats it using YYYY it changes it to 2018.

Sorry for the inconvenience.. this has never been seen before as we are a bit surprised by this behavior. We have submitted a support case with Salesforce and will update this post once we hear back.

[CoralReefAlliance]

Hi there,

Thanks so much for looking into this. I've extended access for our instance to be upgraded and will wait to hear back. We'll be curious to see what they say!

[CnP.Support]

Good day CoralReefAlliance

We have identified the issue. Strange indeed - this issue, if surfaces, only shows itself up the first of the year or the last year.

There are 2 formats for year, YYYY and yyyy - one is upper case and one is lower case. Based on tier 2 support at Salesforce we have used YYYY which is week year and not calendar year. When I first heard this I had no idea such a thing exists..

Here is the reference: https://stackoverflow.com/questions/...mpledateformat

YYYY >> Week Year

So the last week of the year the YYYY returns next year.

Sorry for the inconvenience. We are working on a patch to release shortly to address this problem.