In older versions of the getTimeParting plug-in, years were hardcoded in to help accommodate some daylight savings logic. While this issue was fixed well ahead of time, many implementations did not have the latest version of the plug-in, and had to scramble to update their plug-in code.
With that said, please take a couple minutes to review your Analytics implementation, particularly around the getTimeParting plug-in.
If you deployed this plug-in through the Common Analytics Plugins extension in Adobe Experience Platform Launch, great! No action is needed at this time.
If you're on v6.2, great! You're on the latest version, and no action is needed at this time.
If you're on v5.0 or above, Adobe recommends upgrading to the latest version. While you won't be adversely affected by the DST issue, it is a good practice to use the latest version.
If you have any questions about this, please reply here in the discussion and I'll do what I can to assist. I hope everyone has a happy, safe and healthy holiday season!
We are currently with version 3.4 for the getTimeParting Plugin. We have updated this with Adobe Analytics extension under Library Management(custom library code) and we have updated till with current year (2021 with daylight date range under the s._tpDST).
In this regard, could you please how we can update the latest version for the plugin?
Copy the code block on that page, which contains the latest version of the plug-in
In Adobe Experience Platform Launch, locate the custom code block containing the old version of the plug-in
Paste the new version of the plug-in over the old version
Important note: The dimension items that the latest version of this plug-in returns is a lot different than old versions. Make sure that you also update variables that reference this plug-in so they contain desired values. Many organizations find it easier to simply start fresh with a new prop/eVar.