Hit for Six by Spring ’23

As we came out of the short days of January into the slightly longer days of February, we ran the latest of our world famous Salesforce release webinars, covering the key features of the Spring 23 release.

If you missed it, you can access the recording here. If you haven’t got time to listen to the recording until the weekend, here’s six features that really stand out.

Personalized Report Filters 

Hopefully the first step on the road to a range of personalization filters, Spring 23 introduces the concept, with the ability to dynamically filter user fields based on the currently logged in user. No more re-running reports with different user names as static filter values! 

View Full Record Share Details 

The Sharing Hierarchy action button presents you with a list of users that have access to a record. Click the View link next to a name to see the reason why the record is shared with them, and if there is anything blocking access, such as a restriction rule. 

Lightning Component References 

One for the developers – the new lwc:ref attribute provides a simple way to access an element in the DOM. No more overloading data attributes, using fake style class names or coming up with complex selectors. Simply define the attribute and access in JavaScript using the this.refs object. 

User Mode Database Operations 

Another one for the developers! Your SOQL queries and DML statements can now respect the field level security and object permissions of the current user, without having to use the Schema describe objects to check if you should be able to read a specific field. 

Customize Collaborative Forecast Pages 

The Lightning App Builder now supports Collaborative Forecast pages. Add custom charts and components to bring the information you need into your forecasts. If you are creating one from scratch, don’t forget to add the Forecasts Header. Otherwise your users won’t be able to select a Forecast Range! 

Flow Reactive Components (Beta) 

Finishing with a Beta feature (so don’t make any purchasing decisions based on it). Flow Reactive Components allow components in the same screen to react to changes made elsewhere.  Previously you’ve had to move to a new screen to take account of the contents of another component, with the associated transaction commit. With reactive components you simply set the input of one component to the output of another. Don’t forget to subscribe to our YouTube channel to see the recordings of all our previous release webinars and much more.