Most Wanted Salesforce Features – Full Salesforce Roadmap

Share this article...

You may have heard about the Salesforce IdeaExchange? It’s the platform that allows the Salesforce community to directly upvote which features they want to see as part of the Salesforce product. Involving customers in influencing the product roadmap has been a core belief of Salesforce’s since they were founded – what better way to develop products customers crave?

The IdeaExchange (released in 2006) was starting to show some flaws. IdeaExchange Prioritization was born! This new system takes the user wish list and marries it up with reality – how Salesforce product development actually happens and taking complexity into account. With each prioritization cycle, we make the big announcement about each feature; when the next cycle swings around, we add the winning ideas to this most popular roadmap overview (after all, the cycles are pretty rapid!) Hopefully you will spot an enhancement, or two, that you are anticipating!

The Idea Lifecycle

There are two sides to the Idea Lifecycle:

  • Ongoing: anyone can submit ideas they think of to the IdeaExchange. Anyone can upvote these.
  • Prioritization Cycle: the product managers create a prioritization list from the most-upvoted ideas 3 times a year. Everyone spends their allocated ‘coins’ on the ideas, those that get the most votes go on the product roadmap!

The Prioritisation List, therefore, is the most wanted Salesforce features (that are also realistic for Salesforce to deliver). It’s a great feedback loop that means customers get heard, but aren’t left in the dark on why popular ideas aren’t up for the roadmap development.

What’s coming up on the roadmap?

Winter ’22 Release (around October 2021)

Lightning Platform: Metadata for Declarative Change Management

“Expanded Metadata support for Declarative Change Management” – including metadata associated with standard objects.

When? est. release: Winter ’22 (around October 2021)

Idea Details

Idea age: 10 years

Points retired: 26,590

Wow, this seems like a sore topic, so it’s great this is in development now! Here’s a flavour of the pain points that Salesforce will be working to solve:

  • “It is frustrating that we need to replicate all picklist changes on standard objects when deploying from sandbox to live as Change Sets do not support standard objects.”
  • Other items that can’t be added include eg. profiles, changes to standard fields, changes to field security,
  • Other limitations in auditing changes, eg. multiple changes across pagination, no date columns like created or modified.

Ps. the Idea thread is worth a read, some…colourful…comments that shed light on how necessary this enhancement will be.

Lightning Platform: Declarative Release Management

“Improved Declarative Change and Release Management” – cloning Change Sets (and possibly more)

When? est. release: Winter ’22 (around October 2021)

Idea Details

Idea age: 9 years

Points retired: 19,650 (17 merged ideas)

Yes, 17 merged ideas. The community has been clamouring for this for a long time!

  • The ability to clone an Inbound Change Set to subsequently use as an Outbound Change Set.
  • This would mean you can ‘relay’ Change Sets upstream (eg. from sandbox (development) → sandbox (UAT) → production) or downstream (the other way).
  • In a nutshell: consistent migration of changes across environments.

The full details are yet to be confirmed on what this enhancement will include. Salesforce are still collecting feedback on this topic, so don’t delay in sharing your thoughts using this survey (see the idea thread for the most up to date information).

NSPS, EDA and Finanical Services Cloud Features: 

Spring ’22 Release (around February 2022)

Analytics: Inline Editing of Reports

“so that you don’t have to drill into each record separately to edit it” – yes, Salesforce standard reports will function like a list view, double clicking in a report to edit the record! I will certainly gain a lot of time back thanks to this one.

Receiving almost double the votes as the other winners, this one is highly anticipated!

When? DELIVERED (in Beta) in Summer ’21

Idea Details

Idea age: 12 years

Points retired: 22,830 

  • Reports to function like list views, which gained long-standing popularity due to in-line editing (reminiscent of Excel). 
  • List views are restricted to one object, whereas reports can include multiple objects, and filters relating to multiple objects. 
  • Reduces the need to create multiple list views and queues.
  • Predicted to have a great, positive impact on report user adoption. 

Custom fields for dashboard gauge values

Gauge components on Salesforce dashboards are very popular with target-driven teams, displaying progress made towards the target, and whether you’re in the clear, or ‘in the red’ – literally. 

Every admin will know that the numbers for the thresholds need to be ‘hard-coded’, by editing the component and typing in the specific numbers for the green, yellow, and red values: 

When? est. release: Spring ’22 (around February 2022)

Idea Details

Idea age: 14 years

Points retired: 14,120 

Salesforce Queues for Opportunities

“Allow opportunities to be assigned to a queue” – Queues in Salesforce prioritize, distribute, and assign records for teams who share workloads. Queues are like holding areas in your CRM, where records wait for a user to pick them up, assign them to an owner and work on processing them.

When? est. release:  Spring ’22 (around February 2022)

Idea Details

Idea age: 5 years

Points retired: 13,990 

After entering a few prioritization cycles, it is finally time for opportunity queues to receive the limelight!

    • This enhancement will be useful for organizations who distribute opportunities without ‘hard-and-fast’ rules, but instead to whoever has capacity in the team.
    • Queues are currently available on cases, leads, tasks, contact requests, orders, service contracts, knowledge articles, and custom objects.
    • Lead queues have been indispensable to sales development/BDR teams across the globe, now it’s time to extend this capability further down the customer lifecycle.

Lightning Platform: Address Field Type

“Add a standard field type: Address”

When? est. release: Spring ’22 (around February 2022) – moved forward from Winter ’23!

Idea Details

Idea age: 12 years

Points retired: 67,730 

  • Admins can add ‘address’ as a custom field on standard and custom objects.
  • The ‘address’ field type already exists but Admins can’t create them – this will open that up.
  • Will prevent unnecessary workaround Admins have been inventive with for years.

To Be Determined (TBD)

Field history tracking for tasks and events

A task or event record can be edited multiple times in its life. The ability to keep track of which fields were changed when, and by who, will be a huge benefit to organisations relying heavily on Salesforce activities for managing rep/agent workload and tracking performance.

Admins will be pleased! “Follow-Up Task” and event workflows (when they’re not wanted) agitate users. Field history tracking proves why a certain workflow fired when it did, providing the evidence when you’re questioned by puzzled users! 

After missing the mark in the May cycle, we see this much-needed enhancement has captured people’s attention, ranking ahead in the prioritization cycle, despite having half the IdeaExchange points that 2nd place (ability to print dashboards) built up over the same time period! Originally expected in the Spring ’22, this has now been moved out, with a new release date yet to be set.

When? est. release: TDB 

Idea Details

Idea age: 13 years

Points retired: 29,720

  • Keep track of which fields were changed when, and by who.
  • Especially needed as tasks & events can be assigned to multiple users (delivered Summer ‘18).
  • Will help Admins prove why certain workflows fired when they did – providing the evidence when questioned by puzzled users!

(now, can we have the same for Campaign Members, please?)


Past releases:

Summer ’21 Release (around May 2021)

Ability to print dashboards

Users will be able to print dashboards directly from Salesforce in an optimised format.

If you’ve ever been asked to print a dashboard before, you will know it’s not easy to simply screenshot it and run to the printer. 

For super Admins, every dashboard ‘tells a story’, which often gets lost when formatting is changed or disrupted when delivered over email or other formats that are not print preview friendly. 

The new ability will be a huge time saver, and will keep executives – and the many people who love something tangible – happy.  

Why has it taken so long? This delivery will be wrapped into the HTML2PDF service. Although it’s in the works, the product team have been transparent that HTML2PDF is a dependency (which is at least 2 releases out). In the interim, they plan to provide a PNG export of dashboards.   

When? DELIVERED Summer ’21

Idea Details

Idea age: 13 years

Points retired: 50,470

  • End goal: full HTML2PDF for optimising dashboards for printing.
  • HTML2PDF is a dependency that is “at least 2 releases out”
  • Interim: PNG export that will aid getting dashboards into a printable format. 
  • No more third-party workarounds, like Snagit!

Spring ’21 Release (around February 2021)

Share Button in Lightning Experience

“ability for users to manually share records with other users”, just as it was possible to in Salesforce Classic.

When? DELIVERED Spring ’21 (around February 2021)

Idea Details

Idea age: 3 years

Points retired: 34,980

An incredible number of votes for a relatively young idea. Since the Salesforce Lightning Experience roll-out became mainstream, the small pieces missing (compared to Salesforce Classic) are being addressed over time. It seems that some organizations have developed custom workarounds to do this – hopefully you will be able to hold on for half a year longer!

  • The ability for users to manually share records with other users.
  • Users can manage who has access to specific records they’ve shared.
  • Especially important for orgs where the OWD (org-wide default) for objects are set to ‘Private’

Winter ’21 Release (around October 2020)

Service Cloud: Email-to-Case

“Prevent Email-to-Case from creating multiple cases on the same email thread” – an end to ‘backend mayhem’ and the ‘infinite email loop’.

When? DELIVERED Winter ’21 (around October 2020)

Idea Details

Idea age: 10 years

Points retired: 7,050 

  • Will avoid creating duplicate Cases when recipients Reply-All to the first email.
  • The solution will use email headers more intelligently to identify Email-to-Case emails one the same thread as one.
  • Will prevent the ‘infinite email loop’ that’s caused headaches in orgs for years (email goes from Salesforce to a customer email address → customer replies with cc email address → generates a new email activity in Salesforce → generates a new case from the email in Salesforce)

The Prioritization Cycle Leaderboards

We heard about the winners, what about the runners-up? The leaderboards below shows us how popular each of the winning features were and which missed the mark with the coin voting. Any ideas that didn’t make the cut (and more) join the next cycle, which commences a couple of weeks following the closed round.

2 thoughts on “Most Wanted Salesforce Features – Full Salesforce Roadmap

  1. Particularly looking forward to Address field types and more useful changes sets!! Exciting stuff. Great post, Lucy!

  2. Some really useful stuff on here! Frustrating that they’ve all been floating around as pain points for a minimum of 9 years though

Add Comment