Salesforce Winter ’27 – Small Updates, Big Improvements!
Salesforce Winter ’27 offers several practical improvements that simplify day-to-day work with reports, list views, permissions, and change history.
Here, we’ll walk through five updates that make it easier to work efficiently, gain a better overview, and manage information in Salesforce.
1. Preview records directly in reports (Beta)
When working with reports in Salesforce, you sometimes need to review individual records to gain a better understanding of the information behind the report’s numbers. Previously, this meant you had to open the record in a new tab or navigate away from the report to view more detailed information. This can make your work less efficient, especially when you need to review multiple records in the same report.
With the new record preview feature, it's easier to access detailed information without leaving the report view.
By clicking the eye icon next to an entry, you can open a preview and view the entry’s details directly in the report. This means you no longer need to open each entry separately to get a quick overview of the information. This makes it easier to review and compare entries while maintaining the context of the report.
This feature is particularly useful when you're working with reports that contain many records and need to check specific details. By reducing the need to switch between different views, you can work in a more structured way and focus on the analysis.
Here's how to enable the feature:
To use record preview, you must first enable the feature in Salesforce settings. Navigate to Setup → Reports and Dashboards Settings and enable the record preview setting.
When this feature is enabled, the eye icon becomes available for records that support previews in reports. By clicking the icon, you can quickly view more information about the record without having to leave the report.
It's a relatively minor improvement to the interface, but one that can make a big difference in your day-to-day work with reports and data analysis in Salesforce.
2. Show only relevant rows in merged reports (Beta)
Joined Reports in Salesforce allow you to combine different types of data into a single report. This is particularly useful when you want to analyze information from several related objects and get a comprehensive view of your business. At the same time, these reports can be difficult to navigate when they contain large amounts of data that isn’t always relevant to the analysis.
A consolidated report consists of several separate blocks, each of which may contain different types of entries and information. Previously, the report could display entries even when corresponding data was missing from the other blocks. This means that the report may contain rows with empty values, which makes it more difficult to identify relationships between different data sets.
With the new feature for matching rows in merged reports, you can limit the report's content to only those rows that have matching data in all blocks. This allows you to filter out information that has no counterpart in the other blocks and create a more focused report.
A concrete example
Suppose you are working with a merged report that contains two blocks. The first block displays accounts, while the second displays active opportunities. The purpose of the report is to identify which accounts have at least one active opportunity.
Without the new feature, the report may also display accounts that lack active sales opportunities, which means that some rows do not contain any matching information in the second block.
By enabling the setting to show only matching rows, you can limit the results to accounts that appear in both blocks. The report will then show only those accounts that have at least one active sales opportunity, provided that the blocks are correctly grouped and filtered.
This makes it easier to analyze the relationship between accounts and sales opportunities without having to go through entries that lack relevant connections.
This feature is currently available as a beta and is not automatically enabled in all Salesforce organizations. To access it, you need to contact Salesforce Support and request that the feature be enabled in your organization.
When this feature is available, it can be used to create more specific combined reports, where the focus is on records with matching information across the report's sections.
This is a useful improvement for organizations that work with complex reports and want to make it easier to identify relevant connections between different types of Salesforce data.
3. Smoother editing directly in list views
The ability to update fields directly in a List View, without having to open each individual record, is a feature that simplifies day-to-day work in Salesforce. With Inline Editing, users can quickly change information in multiple records directly from the List View, which reduces the number of clicks and makes it easier to keep data up to date.
In the past, however, there have been certain limitations that have affected how and when in-line editing can be used. The latest Salesforce release introduces two improvements that make the feature more flexible and available in more situations.
Edit fields that are not included in the page layout
Previously, a field had to be included in the record's page layout in order to be edited directly in a list view. This meant that users were not always able to update a field from the list view, even though they had the appropriate permissions to edit it.
With this new enhancement, this requirement is removed. This means that users can now edit fields directly in the list view even if the fields are not included in the current page layout, provided they have the necessary permissions and the fields otherwise support direct editing.
This change provides greater flexibility when designing page layouts and list views. Administrators no longer need to add fields to a page layout solely to make them editable in a list view.
In-Place Editing in List Views with Multiple Record Types
Another previous limitation was that direct editing did not work in list views containing records with different record types. If a list view displayed multiple record types, users therefore had to open the records individually to update the information.
With this new enhancement, it will be possible to use in-place editing even in list views that contain multiple record types.
This is particularly useful for organizations that use Record Types to manage different business processes within the same Salesforce object. Users can now work with and update information in a shared list view without having to create separate views for each record type just to use in-line editing.
Here's how to enable the features:
Both of these enhancements are managed through Salesforce settings. To enable them, navigate to Setup → User Interface Settings, where you'll find the settings for direct field editing of fields missing from the page layout and for list views with multiple record types.
Once the settings have been enabled, users can take advantage of the expanded functionality, provided they have the appropriate permissions and that all other requirements for direct editing are met.
Although the changes may seem minor, they represent a clear improvement in the user experience. By removing two previous limitations, it becomes easier to update information directly in list views, while administrators gain greater flexibility in how Salesforce is configured.
4. New Permissions for Setup Audit Trail – Better Control Without Unnecessary Access
Setup Audit Trail is an important feature in Salesforce that allows you to track and review changes made to your organization’s settings. The feature shows which configuration changes were made, when they were made, and which user made them. It provides administrators and security managers with greater visibility into changes that may affect your organization’s Salesforce environment.
Previously, users needed the "View Setup " permission to access the Setup Audit Trail. However, this permission grants access to significantly more parts of Salesforce Setup than just the change history. As a result, users who only need to review configuration changes have also gained access to other administrative information that is not necessarily relevant to their job responsibilities.
With this new enhancement, a separate permission to view the Setup Audit Trail has been introduced, making it possible to grant users access to the change history without also having to assign the broader "View Setup" permission.
More Flexible Access Control
The new permission makes it easier for Salesforce administrators to control which users can review configuration changes in the organization.
One example is an organization where employees on the security or compliance team need to regularly check what changes have been made in Salesforce. Previously, these users might have had to be assigned the "View Setup" role to access the change history, even though they had no need to view other administrative settings.
With this separate permission, administrators can now grant these users access to the Setup Audit Trail without also giving them broader visibility into the Salesforce configuration. This makes it possible to tailor permissions more specifically to users' roles and responsibilities.
Improved support for security and access control
This improvement is particularly relevant for organizations that follow clear security procedures, maintain internal controls, and regularly review system changes.
By separating access to the Setup Audit Trail from the general "View Setup " permission, it becomes easier to adhere to the Principle of Least Privilege. This principle means that users should only have access to the information and functions necessary to perform their job duties.
This new permission thus gives administrators greater control over access to the revision history and reduces the need to grant broader administrative permissions than necessary.
It is a relatively minor change to the Salesforce permissions model, but a valuable improvement for organizations that want to combine effective review of configuration changes with more structured and secure permissions management.
5. User Field History Is Finally Here (Generally Available)
Field History Tracking is a well-established feature in Salesforce that allows you to track changes to specific fields on an object. Among other things, this feature is used to improve traceability, facilitate troubleshooting, and give administrators insight into how information changes over time.
Previously, Field History Tracking was available for many standard and custom objects in Salesforce, but not for the User object. This meant that organizations wishing to track changes to user information—such as when a user was assigned a new profile, role, or manager—had to use custom solutions or in-house code.
This new enhancement introduces support for Field History Tracking on the user object, which makes it possible to track changes to user data directly using Salesforce's standard functionality.
Track changes in up to 20 fields
With this new feature, administrators can enable change tracking for up to 20 fields on the User object. For each change that is recorded, Salesforce can show the field’s previous value, its new value, when the change was made, and which user made it.
This means that administrators will have better tools for tracking how user information changes over time, without having to create separate solutions to record these changes.
This feature can be useful, for example, when a user’s profile or role changes and the administrator needs to determine when the change was made. It can also help with troubleshooting access-related issues, where changes to the user’s settings may be part of the explanation.
The data that can be tracked depends on which fields Salesforce supports for history tracking.
Here's how to enable Field History Tracking for users:
To enable this feature, navigate to Setup → Object Manager → User → Set History Tracking. There, you can enable history tracking and select which fields on the user object should be included.
This configuration works similarly to audit trails for other Salesforce objects. Once the feature is enabled, Salesforce begins logging future changes to the selected fields. Changes made before the audit trail was enabled are not logged retroactively.
The history is retained for up to 18 months in the Salesforce user interface, in accordance with the standard retention period for Field History Tracking. For organizations that require a longer history, it may therefore be advisable to review how the information should be archived or exported.
Greater control over user administration
Support for audit trails on user objects is particularly valuable for organizations that work with structured user management, security, and compliance.
Being able to review changes to user data makes it easier to identify when a change was made and who was responsible for it. This improves the conditions for both internal monitoring and troubleshooting, while reducing the need for custom functionality.
This improvement also means that administrators can use a more consistent approach to audit trail tracking, whether for business-related objects or user information.
Would you like to know more?
In Salesforce's official Release Notes, you'll find all the new features, more detailed information about the features, and instructions on how to get started.
Article written by
Simon Hellberg
Growth Lead, Salesforce
Contact us today
Email us at info@releye.se