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?

  • This question not really about the Stack Exchange, but now it's in the Close Vote queue for being Primarily Opinion Based. I kind of agree that it's not really on topic for the main forum. Can we migrate it back?
    – Adrian Larson
    Oct 17 '16 at 0:46
  • 2
    I also thought it fit better in the meta... there are tons of questions in there that are not directly related to this form in particular...
    – NSjonas
    Oct 17 '16 at 1:40
  • Moved back to meta meta.salesforce.stackexchange.com/questions/2361/…
    – Matt Lacey
    Oct 20 '16 at 3:59

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.

  • 6
    I actually disagree with Private class variables should not be included by Json.Serialize. This should be controllable through Attributes though (@JSONIgnore)
    – NSjonas
    Oct 11 '16 at 18:19
  • 3
    Remember static variables set during testSetup annotated methods maybe? If people like it, add it to the list.
    – sfdcfox
    Oct 12 '16 at 4:15
  • 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. Oct 12 '16 at 16:04

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
    Oct 12 '16 at 12:07
  • 2
    does marketing not hold anything sacred? i mean it's physics guys Oct 12 '16 at 16:00
  • 1
    You canna change the laws of physics. Voted.
    – Adrian Larson
    Oct 12 '16 at 16:51

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.)


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.

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.