As we head into spring here in Australia, Salesforce headquarters are heading into winter and with this comes the Salesforce Winter Release Notes 23. The SalesFix team have been busy reviewing what is coming up and there is excitement for many new features.
As there is a lot of information to digest we have asked our team to give us their top picks from this release from both Salesforce and MCAE (Pardot) that they think will be of benefit to our customers. If you would like to explore more yourself you can find the full Salesforce Winter Release 23 notes here.
Let’s get started with our Winter 23 picks for Salesforce:
Dynamic forms for Accounts, Contacts and Opportunities
You can now get more flexibility with your record page layouts using dynamic forms. This is now available for Accounts (including Person Accounts), Contacts and Opportunities.
“The more fields that you have on your page layout, the more that the Record Detail component becomes a monolithic block of fields that you can’t customse. With Dynamic Forms, you can migrate the fields and sections from your page layout as individual components into the Lightning App Builder. Then, you can configure them just like the rest of the components on the page, and give the users of that page only the fields and sections that they need.”
Add Field Level Security to Permission Sets at field creation
Implementing Permission Sets as best practice is getting easier with the ability to add FLS to a Permission Set when the field is created, a big time save for your admins.
“When you create a field on an object, you can follow best practices and set field-level security for a field on permission sets instead of profiles. And rather than manually granting access to a field in each permission set, you can set field-level security on permission sets during field creation. This feature is also available when you set field-level security on a field or change the field type on a field.”
Create custom address fields
Create compound Custom Address Fields, complete with the Google lookup just like the Standard fields. Be sure to check out the limitations before you enable this new feature.
“To improve address data accuracy and your users’ experience, create custom fields that mimic the behavior of standard address fields.”
In and Not In operators for Flows
In and Not In operators can finally be used in Flows without using the Loop element. This makes it much simpler to find related records using Get, Create, Update and Delete elements
“With the new In and Not In operators, a flow accesses a collection of primitive values to get related records without using the Loop element. The flow uses fewer SOQL queries and DML statements, and performs faster. The new operators support accessing collections of type Text, Number, Date, Date/Time, Currency, and Boolean. The operators are available in the Get Records, Update Records, and Delete Records elements.”
Update Related Records for Record Triggered Flows
Updating records related to the record that triggered the flow is now possible with a Flow, another step towards Process Builders eventual retirement
Enhanced Domains enforced in Winter ‘23
If you haven’t already switched to Enhanced Domains now is the time. Enhanced Domains will be enforced for sandboxes and non-production orgs this release, and for production and remaining orgs in Spring ‘23;
“To comply with the latest browser and security standards, enable enhanced domains on My Domain. Enhanced domains also comply with the latest browser requirements, allowing your users to access Salesforce using browsers that block third-party cookies. Because this update affects application URLs, including Experience Cloud sites, Salesforce Sites, and Visualforce pages, we recommend that you enable enhanced domains before this update is enforced.”
SalesFix Winter 23 picks for Marketing Cloud Account Engagement (Pardot):
Bring Third-Party Apps to life within Account Engagement (FKA, Pardot) with Extensibility Enhancements
As part of the latest round of innovations within Account Engagement, you can now implement third-party actions to Prospects outside of the standard Account Engagement actions that come out-of-the-box.
For example, automatically register prospects for webinars, send SMS texts, create new Salesforce leads, and use these actions and more as part of your ongoing Engagement Studio campaigns. These require some setting up and Developer knowledge, but these actions take MCAE one step closer to being the single, marketing-point-of-truth it aims to be.
Sync All Prospect Records with a Single Click
A nice and simple improvement, the aptly-named ‘Sync All Prospects’ option to sync prospect records with Salesforce allows you to quickly stay on top of your syncing issues. Previously, a prospect field needed to be updated in order to trigger a full sync.
Stay GDPR-compliant with changes to the standard Prospect Opt-Out Status field
Previously, Account Engagement allowed for the standard Prospect Opt-Out Status field to use the “Use the most recently updated record” Sync option. With hindsight, this allowed for situations where a Prospect’s Opt-Out Status could be overridden by inadvertent changes to the field, distorting the point of truth – and potentially opting-in Prospects who had previously unsubscribed. This latest change removes the “Use the most recently updated record” Sync option, resolving this issue.