It looks like Salesforce installed a managed package called SalesforceIQ Inbox on our org back in 2019. Does anyone know what this does? I need to know if there's a way to upgrade it or if I can remove it as it's got Apex code that has an API version of 39.0.
The managed package is no longer required for Inbox functionality and can be uninstalled.
Hey all — quick question regarding some date parsing deep-dives in an ICU-enabled org (locale testing). I'm noticing this behavior:
start :
Date d1;
try {
d1 = Date.valueOf('2024-05-21'); // ISO format, always works
} catch (Exception ex) {
System.debug('valueOf failed');
}
try {
d1 = Date.parse('2024/05/21'); // Fails on en_GB, works on en_ZA
} catch (Exception ex) {
System.debug('parse failed');
}
System.debug('Locale: ' + UserInfo.getLocale());
end:
It seems Date.parse() is
locale-sensitive (e.g., en_GB expects dd/MM/yyyy), while Date.valueOf() is locale-agnostic
as long as the format is ISO.
Q : For ICU-enabled orgs — what should we watch out for when working with dates and numbers
(e.g., decimal separators or thousand groupings)? Any gotchas that can break functionality or cause silent failures in dates, formulas, Apex, or integrations?
@* Salesforce Developers * @ICU Locale Formats Adoption @Michael Brown @Vaibhav Mankame
Adding a couple of relevant references for anyone running into similar ICU / locale-related issues:
https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code_methods.htm&type=5
https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code_examples.htm&type=5
,
I am trying to enable ICU Locale in the sandbox. I have just enabled it for testing, and it shows this step to me.
Hello, I'm not sure if this is the right place to post this but the bug created for NPSP in regards to low API versions has a Solution Scheduled status but it doesn't say when we are getting that solution. Any idea?
@Katie Kourtakis Upgrade has already been delivered as part of Summer '25. It appears that the status of the issue has not been updated.
Hi,
A couple of our clients had problems with updating API versions. However, we're able to resolve it. We would like to finish this change, as the clients are not sure if everything is correct. We've enabled the change using Release updates. Is there anything else we could do to enforce the change or the only way is to wait till May, 2026 release?
Thank You in advance
Jan Strzemiński
,
You still have time then. Final date is May 2026
Ref -
https://help.salesforce.com/s/articleView?id=000380618&type=1
To manually enable use following article -
https://help.salesforce.com/s/articleView?id=xcloud.icu_migration_enable.htm&type=5
Thanks
Hi, as the title says, I was wondering if I need to update the API version for every single Apex class / trigger or Visualforce page in our org, regardless of if its Status is Active, or other criteria? I ask because based on a this simple SOQL query I ran we have nearly 2000 Apex classes that would need to be updated:
SELECT Name, ApiVersion FROM ApexClass WHERE ApiVersion < 45.0
Am I misunderstanding what i need to update, or do I really need to update the API version for all of those? And if I don't need to, then how do I determine which classes, triggers, etc that I do need to update?
Hi Lex,
In our experience, we have updated — and continue to update — many resources such as Apex classes, triggers, Visualforce pages, etc. If you have any active or inactive classes with an API version lower than 45, the release won’t be applied automatically. However, you can activate them manually while your team works on updating the related code.
It’s possible that some of those classes don’t have associated test classes, since years ago this wasn’t always required. In our case, we found several classes — for example, from 2012 — that had no test coverage, and we had to create test classes because they are now a mandatory requirement to deploy to production.
I recommend doing a deep analysis beforehand — some classes may be deprecated or no longer in use and can be safely removed from production.
Unfortunately, there’s no quick way to make these updates; it has to be done one by one. If you have a UAT org, you can activate this manually and verify that nothing breaks, allowing you to focus on any areas that need attention.
ICU Local Formats - Need some guidance and advice as I have recently taken over the sys admin role in a new company and i can see presently that we have a few managed packages with APEX <45 within our production enviroment that are not necessarily integrated yet have dependencies - so i cannot uninstall the legacy package until we divorce the dependencies. Ive installed the new updated packages that are ICU supported but they have a different naming convention so hence dont update the existing package... My question is - how do i divorce the dependencies so that 1. I can uninstall the legacy package and 2. Enable the new package.
Asking as keen to finalise testing and adopt ICU asap given we have had a notification to say that it failed recently with Summer 25 update
HI , we have a couple of classes where we receive a HTTPResponse with date time fields in form of a string
"2023-10-19T00:00:00.000Z".
we use a wrapper class where we simply push this onto the respective fields in salesforce ( here a datetime type)
Do I need to change anything or will this still work with ICU?
I just wonder if this error message has something to do with it
"Character t is neither a decimal digit number, decimal point, nor "e" notation exponential mark"
due to the fact that i couldn't find any "t" in the JSON except in the datetime a capital T
There's a few Apex classes that have version < 45 still. Does anyone know if the update has to wait until the CPQ Summer '25 release in production? https://install.steelbrick.com/
We're getting the overall release at 1:00 am on June 7, and then I see the CPQ release is scheduled for 2:30 AM. Won't the ICU locale enablement fail then?
Thanks!
In the Summer '25 pre-release org, this is what the ICU Locale Formats release update shows:
What exactly is happening? There is still a lot of confusion around this update and the plans still seem to be changing. There have been notifications that it isn't going to be enforced, but this shows it now will be? There has been information that for Summer 25 the release update cannot be postponed but this indicates it can be.
OK, thank you for confirming.
The wording "Enablement unsuccessful" indicates that the update was attempted and failed.
We can contact our customers to let them know they will receive an email when their org/sandbox is updated to Summer 25, and refer to the Salesforce Known Issue and Knowledge Article.
Thank you.
Sarah
