23

Experience:

I am quite new to Salesforce and I've just gotten access to the Salesforce Stack Exchange. Because I am new here I would like to integrate it as a part of my workflow with Salesforce so that I can learn fast.

Questions:

How specific do I need to make my question so that I can get a usable answer? How much research should I do before posting a question?

migrated from salesforce.stackexchange.com Dec 28 '16 at 16:17

This question came from our site for Salesforce administrators, implementation experts, developers and anybody in-between.

  • You should start by asking this sort of question on Meta instead. – Adrian Larson Dec 28 '16 at 16:00
  • 5
    You can start by reading the Help center if you haven't already. Also, use findsf.info to search for answers to your question before asking them here. – crmprogdev Dec 28 '16 at 16:11
  • 1
    And a big Thank You for taking the time to ask this question. – Sebastian Kessel Dec 28 '16 at 16:31
  • Upvoting useful answers you receive and accepting the answer you found the most helpful toward resolving your issue is something that's also important to the community and those who might later read your question. – crmprogdev Jan 5 '17 at 15:20
  • Just try, it's extremely frustrating when someone says I need a Trigger to insert a record.. Remember we are here to help you do your work, not do your work. – EricSSH Feb 11 '17 at 9:49
20

It is important for you to demonstrate a basic understanding of the subject matter before posting your question. If you're not sure where to start, definitely look to Trailhead, as that is a site geared towards learning the platform. Posts about basic platform functionality that is well documented are frowned upon (and usually negged). As long as you can show that you made an attempt to learn the subject matter, you should be fine.

Bad Question

How do I write a batch to do X?

Good Question

I tried to write a batch to do X, but I got stuck because of error Y. Here's my code and the verbatim error message.

Always include error messages verbatim when you experience an error. It can be frustrating to come across a question that just says "it doesn't work" or "I got an error". It shouldn't be a guessing game here. The more specific you are about what you have tried and why it doesn't work, the better answers you will get.

The flip side of that specificity is, you should try to identify what portion of your code is relevant. The process of learning your own code well enough to pinpoint a specific function or query that is giving you trouble will make you a better programmer, and make your posts more broadly applicable. It's no fun to read through someone's 200 line controller when they really just needed help with one query.


How much research is enough? You should do as much research as practicable. If you can solve your own issue without a need to post it, that's a win! If that question has already been asked on the Salesforce Stack Exchange and the answer helped you, upvote both! If you found the answer elsewhere and want to share your discovery, then feel free to ask and answer your own question.

On that last point, I advise slight caution in making ask-and-answer posts while you are still a beginner. If you post an especially trivial finding, or if the general question has been answered many times on the exchange, you may receive a negative response. However, if you post such findings in good faith, we don't tend to be too harsh. As you gain more experience with both Salesforce and the Stack Exchange, you will get a better sense for which findings are trivial and which are meaningful.


A few updates from the comments

The best case scenario for your code snippets is that they will not be so wide or tall that we have to scroll to read it. I'd say width is marginally more annoying to scroll through than height. As a rule of thumb, that's ~90 characters to a line (92 if you want to push it) and ~38 lines.

That's not a lot of real estate, so make it count! Separation Of Concerns tends to make it easier to break out a few distinct snippets, if you have more relevant code than you can include in one such block. If you can't coherently organize distinct snippets, however, it is better to include one long block than several shorter ones that are hard to piece together.

I have a few recent examples of ask-and-answer you might find insteresting/instructive. I don't want to imply by any means I set the best example on the Stack Exchange network, but if it helps you find your way, I'm happy to help.

Looking forward to your contributions.

  • Yes agree, it 's really irritating when some one just ask.'Please do the code for me ' =) – unidha Dec 29 '16 at 9:29
  • 4
    i'd even go so far as to have OP strive to fit properly indented code sample so no scroll bar appears. I know if I have to scroll more than one page down, I tend to not want to answer. (N.B. You might want to link to one of your own ask-answer sequences as a best practice) – cropredy Dec 30 '16 at 2:17

You must log in to answer this question.

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