Salesforce Winter ’22 Release

Some great new features released. Here are a few of our favourites.

Dynamic Gauge Charts

Dynamically update gauge target performance values with values from the underlying report. Without this feature the target performance value had to be manually updated. Details here.

Control access to sensitive data

Previously some record visibility was exclusively governed by the parent record visibility. For example, a Task or Event’s visibility is based on the related Account’s visibility. If the Account publicly visible so were the child tasks and events.

This update allows for a further level of restrictions to be applied. Details here.

Org-specific performance analysis of lightning page performance

Lightning page performance has been a user bugbear from day 1. This tool gives you Org-specific metrics on page performance during the last 90 days. This highlights the worst and best performing pages. Details here.

There is a lot to unpack. Not least of which is all things Flow. Flow is set to be the future for workflow automation and will completely supplant Process Builder at some point.

Full release details here.

Issue with role hierarchy reporting in Lightning

If an Org has two nodes immediately below the prime node there is an issue with including all records owned by users in these two nodes.

Under the prime node CDV there is a CEO and a Co CEO node.

role hierarchy

When defining the scope of records in a report filter the prime node, CDZ, cannot be selected.

report role selection

A choice has to be made between one or the other CEO node.

report two nodes

This is not a problem in a list view since all opportunities can be selected in the record scope without having to choose a node other than the prime node as is the case for reports.

The workaround is to either use a list view or create the report in Classic where all opportunities can be selected. Note that if you edit the report in Lightning after it has been created in Classic it will assume the above behaviour and the report will be limited to the first CEO node.

Update (4th Nov 2018): This is a known issue and will be fixed in a Winter ’19 patch