Its 2018

Welcome to 2018 yall. There was a recent post on the hub that got me thinking about my long running list of random stuff that as far as i know you still cant do in salesforce, even in the year 2018.

So here they are, in no particular order. Some of these may be fixed in lightning already, which i will find out later this year when we launch!

  1. you cant remove the submit for approval button from the approval history related list. especially considering that you can now submit for approval via flow and process builder now, admins need to be able to remove the standard button. idea : 5120 points, 10 years old, ‘under consideration’

  2. the lack of a description field on public groups. public groups are used literally everywhere, and there is no easy way to extract the info on where they are used. i’ll take 255 characters, anything at all really, please? idea : 11 years old, 1550 points and another idea w 350 points

  3. cant map to the standard contact other phone field on lead conversion. lead has two standard phone fields : mobile and phone. contact has three : mobile, phone, and other phone. so, if you want to map other phone from lead to the contact standard field, you need a hidden dummy field + a workflow rule. sure that works, but why have 3 fields on contact and 2 on lead - just make them match up and happiness shall flow.

  4. on the opportunities related list on contact, you cant view the contact’s actual role on the opportunity! And the same goes for the ‘is primary’ checkbox as well. those are really really important. idea: 2691 points, 8 years old and then there is the idea to make them customizable - 9370 points, 8 years old, or even a first class object - 12,090 points, 2 years old.

  5. we cant use salesforce mobile app to access the trailblazer community. its all your own product - make it happen! i know there are two bazillion users now, but lets dial it to 11! idea : 4670 points, 3 years old

  6. you need to use a formula field to view primary campaign source on opportunity related lists and to filter on primary campaign source in standard opportunity reports. because, who doesnt like adding clutter just to be able to report on stuff that is already there b/c you can just add a formula field and voila. so, like, fix that please. idea for list views : 4080 points, 11 years old - somehow the idea for reports is marked as delivered, but only if you run a campaigns with opps report, and that is not the point.

  7. the ‘parent case’ field is not available on the case close layout. ok, its probably not a thorn in many people’s sides. but, why? someone must have gone the extra mile to prevent that field from showing up as an option on the close case layout. at least give a reason! idea : 330 points, 3 years old

  8. cant rename owner on custom objects - even though the idea is marked as delivered. it can be renamed on standard objects. sometimes owner doesnt really convey what we are after. its kinda old-fashioned if you think about it. so let me rename it please! idea : 2290 points, 3 years old

  9. Opp amount and expected revenue fields are not available on standard campaigns with opportunities report type, but are available w formula fields. i had this one noted down before and will take my own word for it, since i have to get back to work.

  10. and last, in case you missed it, you still cant remove the submit for approval button from the approval history related list. even though its 2018.

BONUS ROUND - adding more stuff as i feel motivated to do so

Trigger case assignment rules from publisher actions. Because, case assignment is typically a non-trivial part of the support process. idea : 2650 points, 3 years old

Multicurrency woes :

Squishy bug-like creatures that are still classified as ideas

Email woes:

Process builder woes:
Waiting interviews - need better info

 
2
Kudos
 
2
Kudos

Now read this

How to throttle an outbound message in Jitterbit

Over the past year, I have been working on a number of integrations using Jitterbit, focused on moving HR data to various systems. We initially went for a transactional approach, where operations would be triggered by outbound messages.... Continue →