We have a couple of Visualforce pages that are in the API set that Salesforce is retiring. RelationshipsSettings and RelationshipsViewer are at version 23.0. They are in the npe4 namespace. Is this something we need to be concerned about?
Hi @Arlene Stebbins ,
However the good news is the API version deprecation only applies to API connections you make between your Salesforce Org and other systems. It does not apply to meta-data inside the org. I can see how it it is confusing for customers but if you take a closer look at this link: https://help.salesforce.com/articleView?id=000351312&type=1&mode=1 you will see this line: "This retirement does not include Custom Apex REST & SOAP Web Services, Apex Classes, Apex Triggers, or Visualforce Pages."
https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000C5NVJSA3
Yes, we have manually enabled it in our sandbox org, but don’t feel good about running code specifically not supported by Salesforce. We are hoping that NPSP will be updated before we must implement it in our production org. We don’t know when that will be enforced. The announcement was that it would be enforced for us in this upgrade. Hi @Rachel Beach ,
Please check this article.
https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000KDaw00AD
Salesforce is recommending we delay the ICU date formats until the next release. Instructions and recommendations here:
https://issues.salesforce.com/issue/a028c00000zketzAAA/unable-to-enable-icu-locale-formats-in-an-org-with-volunteer-for-salesforce-v4s-nonprofit-success-pack-npsp-installed-due-to-low-api-versionsThank you. I hadn't picked up on that detail. However, we still have a problem with those old versions. The new ICU date formats are due to be enforced in our org next month. All of our locally-developed code have new API versions, but some of the NPSP items do not. The email we received from Salesforce about this during our sandbox upgrade to Spring '25 reads:
Your sandbox org (id removed) was not enabled on the ICU locale formats as notified due to the API version below 45 used in the org.
Please upgrade your Apex classes, Apex triggers, and custom Visualforce pages to API version 45.- or higher. For details, refer to the Help article API Versions for Apex Classes, Apex Triggers, and Visualforce Pages.
Salesforce will make this update to your Production org in the following weeks. After the change is completed, you’ll receive a follow-up email confirmation.
For questions about the phased deployment, refer to the knowledge article JDK Locale Format Retirement and Enable ICU Locale Formats Release Update.
Is there any way to get those API versions updated?
I have the same issue @Vince Rice
, I updated npsp, but these two classes are currently still API version 26 and 28.
Have you had to defer the update to summer, or did you find a resolution?
I have the same question as @Vince Rice... @Keiji Otsubo
are you saying that if we manually enable the ICU locale that we will have addressed the concern from the "Your Salesforce Release Update Enforcement Was Unsuccessful" email? The email says "The enablement failed because this org contains one or more Apex classes, Apex triggers, or Visualforce pages that are using an API version less than 45.0" but I was actually able to enable the ICU locale formats and I didn't see an error.
So maybe we're ok even though we have the older API versions for those npe4 packages?
Hi @Arlene Stebbins ,
I received the same email, so I checked with the Japanese support team.
The environments that received this email (organizations with Visualforce/Apex class/trigger API versions below 45.0) have not been automatically enabled, but it is possible to enable it manually.
Instructions for manual activation can be found in the following help article:
https://help.salesforce.com/s/articleView?id=sf.icu_migration_enable.htm&type=5
We plan to eventually enable the ICU locale for all organizations.
We apologize for the inconvenience, but we would appreciate it if you would consider manually enabling it and testing its operation in preparation for the ICU locale being enabled.
I was coming here to ask the same thing re the ICU date formats. They won't update as long as we have API < 45, so the Relationships_INST and test class are still a problem. Can we get these updated to a more recent API?
