Ideas that every salesforce developer should vote for?

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.

  • Ability to update Metadata from Apex (Apex Metadata API)
  • Add "Switch" or "Case" Statement to Apex
  • Add Apex API for Custom Labels
  • Allow debug log filtering for test methods
  • Allow Record Name to be formula field while allowing autonumber
  • Allow SOQL GROUP BY on formula fields
  • Apex Code: Implement Iterable on Set.
  • Apex Enum parse from string
  • Apex String.format() should take Object[] instead of String[] for arguments
  • atExit" support for Apex Code
  • Create an exception class that throws warnings for governor limits
  • Expand Apex System Assertion methods to handle nulls and type checking.
  • Get RecordTypeInfos by API name method
  • Insufficient Privileges - Tell me why
  • JSON Serialization Annotations
  • Lambda Expressions
  • Make Database.upsert Throw Errors at Run-Time Instead of Compile-Time
  • Null Coalesce Operator
  • Private class variables should not be included by Json.Serialize
  • Proper Class Reflection
  • Proper Namespacing
  • Provide an additional addError method on SObject that accepts a field name
  • Remember static variables set during testSetup annotated methods
  • SANDBOX - REFRESH ABILITY BETWEEN SANDBOXES
  • SObject model extension classes
  • Support Field-sets in SOQL SELECT clause

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


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

  • Personally, only the lack thereof on OpportunityContactRole (idea link 1, idea link 2) impacts me.

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

Tags:

Ideas

Recent Posts