#New Releases42 debatiendo

Hi Robert,

For the ICU Locale Format migration, I would recommend treating it as a testing/impact-assessment exercise rather than just changing the setting.

A few things to check:

• Review the Salesforce ICU Locale Format Migration documentation and identify which locales your org uses.
• Test date, time, number, currency, and address formatting for your supported locales.
• Pay particular attention to Apex, Visualforce, LWC/Aura, integrations, reports, and any custom JavaScript that parses or formats dates/numbers.
• Test automation such as Flows, validation rules, formulas, and email templates where locale-dependent values are involved.
• Test integrations carefully if they exchange formatted dates/numbers with external systems.
• Enable ICU in a sandbox first, run regression testing, and compare the results with the existing format.
• Document any impacted customizations and update them before enabling it in production.

The main risk is usually custom code or integrations that assume a specific date/number format rather than Salesforce's locale-aware formatting.

If you share which Salesforce products/customizations you're using, I can suggest a more specific migration checklist. 

Hi Branden, 

Changing the minimum password length in Salesforce Password Policies does not immediately change or invalidate passwords that existing users have already set. 

The new policy applies when users set or change their passwords going forward. Existing passwords can remain as they are until the user changes/resets the password. 

If you want to force existing users to comply with the new password policy, you would need to have them reset their passwords (or use an appropriate administrative process). 

Hi Bob,

If you're referring to Enhanced Notes, you can automate this using the ContentNote and ContentDocumentLink objects. 

One approach is to use a record-triggered Flow on ContentDocumentLink to detect when a note is linked to the record, then send an email notification to the appropriate users. 

Keep in mind that ContentDocumentLink is used for linking the Note to records, so you'll need to determine the linked record and recipients before sending the notification. 

If you share which record you want to notify users about (Account, Contact, Opportunity, etc.) and whether you're using Enhanced Notes, I can suggest the exact Flow configuration. 

Hi Afe,

A good way to isolate whether a trigger issue is release-related is to compare the same functionality in an environment that has not yet received the release.

I would suggest:

• Reproduce the issue with the same data and steps in both environments.
• Check the debug logs and identify the exact exception or line where the trigger fails.
• Review the Salesforce release notes for changes affecting the object, trigger context, Apex, APIs, or related platform behavior.
• Check whether any recent metadata, managed package, Flow, validation rule, or permission changes were also deployed.
• If the trigger works in the pre-release environment but consistently fails after the release with no code/configuration changes, that is a stronger indication of a release-related regression.

If you can share the exact error message and trigger behavior, it would be easier to narrow down whether it is a code/configuration issue or a Salesforce release issue. 

Hi Fabian, 

Two separate reasons, per official Winter '27 release notes: 

1. "Compare Values Between Fields in SOQL" (FORMULA() in WHERE clauses): requires API version 68.0+, and is scoped to sandboxes/Developer Editions/scratch orgs only. If your sandbox's API version isn't bumped to 68.0+ yet, it won't show even on Winter '27. 

2. "Preview Records from Lightning Reports Without Losing Context": ships as Beta with Salesforce's standard disclaimer that beta features aren't guaranteed to roll out simultaneously with GA features, even within orgs already on the release. Some Winter '27 betas explicitly require Salesforce Support to switch on (e.g., "Show Only Matching Records Across Blocks in Joined Reports" says exactly that), so it may need manual enablement rather than a Setup toggle you're missing. 

Reference:

Next step: confirm your sandbox's API version for #1, and if #2 still doesn't appear, open a case with Support to check if it needs manual enablement on their side.

@Eric Burté

I am in the release readiness channel. I suppose my questions are targeted towards the product team for health cloud/home health and this being the group for that it seems like the best place to post it. I don't want/nor think I should need to cross-post. 

Yes I have already checked the component config. There are no additional undocumented parameters that I could use.