I've noticed that Ideas around improvements to the apex language don't seem to get the same up-vote exposure as some of the admin-based improvements.

Thinking this might be a good place to aggregate all the ideas that we should be all voting on (for the sake of modernizing development on the platform).

Here are some of my top:

Proper Namespacing

Proper Class Reflection

Lambda Expressions

Support Field-sets in SOQL SELECT clause (disclaimer, I submitted this one)

JSON Serialization Attributes

What other ideas should we all be voting for?

5 Answers 5


Good Dev Ideas Community Wiki (no judgement, a-z, if you think it's worthwhile just add it, don't remove ideas added by others).

Vote for everything you agree with to build visibility. If you have opinions on them or disagree with them, comment/downvote on the idea exchange.

Archive: The following items have been delivered, or were archived due to inactivity, and can no longer be voted for.

  • 8
    I actually disagree with Private class variables should not be included by Json.Serialize. This should be controllable through Attributes though (@JSONIgnore)
    – NSjonas
    Commented Oct 11, 2016 at 18:19
  • 2
    Remember static variables set during testSetup annotated methods maybe? If people like it, add it to the list.
    – sfdcfox Mod
    Commented Oct 12, 2016 at 4:15
  • @sfdcfox I personally disagree with that one, but there's no harm in adding any Idea to the list. No one is twisting our arm to actually vote!
    – Adrian Larson Mod
    Commented Oct 12, 2016 at 13:22
  • 5
    we're developers, there is 0% chance we're all going to agree on this list, so if you think your idea is controversial, add it anyway. please be sure to channel any opinions into the idea exchange so the salesforce pms can see. Commented Oct 12, 2016 at 16:04
  • New one from @Matt Lacey - success.salesforce.com/ideaView?id=0873A000000cMjzQAE
    – Dave Humm
    Commented Nov 4, 2016 at 15:58
  • Anybody have insider connections to the people who develop for us to make them aware of this thread? I just added "Update API call should allow External ID like Upsert call does" and noticed that people there are complaining that it's a common-sense request that's languished for 8 years without so much as a word of reply from Salesforce - probably because it's lost due to too few upvotes. We can only do so much with our upvotes ... but if Salesforce is combing this post, watching for things we care about, maybe that'll REALLY help surface this kind of thing?
    – k..
    Commented Dec 13, 2016 at 19:08
  • Removing ENTER_MANAGED_PKG from debug logs has been delivered. Commented Apr 4, 2018 at 16:54

Split from the community post as this answer as it isn't really developer related.

What is your first thought when you see the proposed Spring `17 Release logo?

Proposed Spring `17 Release logo

If something in your head starts going Roy G Biv, then this is the idea for you:

Correct the color ordering in the Spring `17 Release logo

  • 1
    voted for it and going to spread it to my community groups in London
    – Dave Humm
    Commented Oct 12, 2016 at 12:07
  • 3
    does marketing not hold anything sacred? i mean it's physics guys Commented Oct 12, 2016 at 16:00
  • 2
    You canna change the laws of physics. Voted.
    – Adrian Larson Mod
    Commented Oct 12, 2016 at 16:51
  • 2
    Looks like this particular campaign was successful. Long live Roy G. Biv!
    – Derek F
    Commented Oct 20, 2016 at 13:51

Definitely had the same feeling (there is even an idea for a separate dev idea exchange, fortunately since the dev stuff has dedicated PM(s) stuff gets picked up with a lot fewer votes than admin stuff.

That said, more visibility never hurts, and I've got a lot close to my heart, created a wiki response for people to collaborate on a group list instead of having 20 different answers.

  • Maybe if dev ideas had a lower threshold, or perhaps we had a better channel for communication?
    – sfdcfox Mod
    Commented Oct 12, 2016 at 4:23

My absolute #1 gripe as a developer is shared w/ admins: "allow triggers (+WF+PB) on objects they're not currently allowed on."

Unfortunately, I think the ideas have been fragmented object-by-object in "Ideas."

But at Dreamforce this year, I learned that there are between 10 & 20 such objects still languishing. Not sure if there's a master "fix all of them" Idea yet, but I'd vote for that if there were.

It's really hard to design proper data models when there are certain tables (especially "junction tables") you can't fire triggers against.

(Firing triggers around tables they link to is not the same, as close as some clever kludges may get.)


New one, since Pardot just announced they're closing down their Idea Exchange:

Enable OAuth Support On The Pardot API

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .