The Salesforce Summer ‘23 release is now available. In it you will find lots of new features, as well as new enhancements related to Lightning Experience, Salesforce Flow, Lightning Web Component, Apex, Experience Cloud, Einstein Automate, Customer Data Platform, Field Service, Marketing Cloud Account Engagement (aka Pardot), Quip, CRM Analytics, Salesforce CMS, Salesforce Payments, Subscription Management, Enablement Sites (myTrailhead), Data Cloud, Financial Services Cloud, Revenue Cloud, Salesforce CPQ, and APIs. There is a lot. To help simplify we have boiled it down to the top 13 enhancements: a baker’s dozen of Salesforce goodies.
Top Features At-A-Glance:
- Set Field-Level Security for a Field on Permission Sets Instead of Profiles
- Enhance Your Visualizations with Images, Rich Text, and Dashboard Widgets
- Focus Your View with More Dashboard Filters
- Get Sales Teams Started with Pipeline Inspection Fast
- Assess the Health of Your Sales Forecasts with Built-In Charts
- Plan Sales Strategies as a Team
- Boost Productivity with Mass Quick Actions on Related Lists (Beta)
- Provide Users a List of Choices for Easy Selection with Choice Lookup (Generally Available)
- Update the Screen in Real-Time using Formulas (Beta)
- Maximize Your Productivity with Calendar Enhancements
- Nail Your Meetings with Salesforce Meeting Digest
- Build Screens with Reactive Components (Beta)
- New Process Creation Is No Longer Available
Feature: Set Field-Level Security for a Field on Permission Sets Instead of Profiles
- When Released: Summer ‘23
- Requires Configuration: Yes
- Difficulty: Easy
- User Interface: Lightning Experience & Classic
- Benefit: Configure field level security on a permission set instead of profile in object manager.
- Salesforce Help Article
When creating a field in Salesforce, you will now be able to set the field level security on a permission set instead of a profile. On top of this, you can modify the field level security for an existing field on a permission set from the Object Manager. With this update, a lot of time is saved when expanding field access through permission sets. This is especially true for Orgs where profiles might be heavily restricted in terms of field level security; now configuring and managing the field level security on a permission set will be easier than ever. You will no longer need to go to permission sets one-by-one and update the field level security. From the Object Manager, you will be able to assign this directly while creating the field, or when modifying existing fields. It’s important to note that, if you enable this setting, you will no longer be able to set the profile field level security when creating a new field, only on the permission sets.