This is my view of (and possibly an update to?) old post by @LandraRobertson Getting fast helpful answers to your questions as a person who answers quite a few posts here in JMP Community. The post is quite lengthy one but hopefully it helps someone.
I have been mostly answering other peoples questions here in JMP community. I just wanted to write a Discussion topic on how you can get help fastest and most likely will have your problem solved (in my opinion). This will be quite a long post, sorry about that! This is also a good place to remind that JMP is Not a Spreadsheet. In the end from the following list number 10 is the most important one, these are just some of my opinions on how you can increase your chances to get correct answers quickly.
1. Search community for similar problems to see if your issue has already been solved before
You can try using JMP Community's search with some keywords or use Google Search (I prefer Google Search). For example to look for how to calculate sum with JMP you could search google with: calculate sum site:community.jmp.com to "force" google to make the search on community.jmp.com website.
Community search
Google with "force" search for community.jmp.com
2. Use descriptive title
Descriptive title will guide correct people to your problem faster. Try to be specific but keep it short. Sometimes just using descriptive title might help you find an answer as JMP Community page will suggest you topics related to that
3. Explain the problem as well as you can
Try to use simple language. You might know the "language" on the field your question is about, but other community members might not but they might still be able to help you solve your problem or take part in the discussion.
From time to time users also ask something and in reality expect to get an answer to something else (XY problem). Some examples for XY problem can be found from The XY Problem and XY problem (wikipedia) .
4. Show your previous work if possible
If you have already tried some solutions, provide them if possible.
5. Provide example data with example of correct answers (and code)
Provide example data set when feasible. Also if you have a problem with Column Formula or some calculation to columns, try to provide result column which can be used when testing solutions. Images of your data table are not proper example data and it slows down the problem as usually solver has to create mock-up data based on the image and it is slow, prone to errors and will sometimes miss some edge-cases. Here are some possible ways to provide data:
- Use attachments in community. You can attach many different types of file types
- Create mock-up data with JMP
- Use real data but remember to anonymize it if required. Also remember to remove data table scripts if they have some sensitive information
- Provide JSL script which will generate example data. Try to keep script fairly short, as long scripts are difficult to read. If the data creation script gets too long, it is better to attach the data table. If the script gets very long, you can try to "hide" it by placing JSL script inside spoiler tags
If you provide example JSL, use JSL script block as it makes the script part much easier to read (and in general the message more clean).
6.Provide example of the analysis/graph you have problem with
Try to provide example of the issue you are having:
- If you have a problem with a script -> provide the script you are having issues with (and possible error from Log window)
- If you have a problem with a graph -> provide script to create the graph or an image of the graph you want to have. Even paper+pen version might guide other people to solve your problem
7. If you do/don't want scripting solution say so
There are lots of ways to solve different problems with JMP. Quite many of us might easily start writing scripts even when it isn't needed (like myself). This won't be helpful if you don't want scripted answer. You can do a lot of different things in JMP without scripting (and after you have done it without scripting, you can most likely easily convert it into a script), here is one such example Re: Bin a defect using a priority list .
8. If you get your problem solved remember to accept correct solution (sometimes there might be many) and give kudos to good posts.
Accepting solutions will mark the post solved and it will also make it easier for future users to find the solution.
9. Use Wish List if there are some features missing from JMP
If you feel like some of your ideas could improve JMP, post them to JMP Wish List.
10. If you cannot provide data, don't have previous work, don't worry just post!
Purpose of these the items is to give you best chance to get quick and correct answers to your questions. Sometimes ending up with an answer might take some discussion between community members to come to an agreement about what is being asked and how it should be approached. In the end if you have a question just ask it.
Some JMP helpful resources:
Some great community posts (not in any specific order and some might be a bit old)
-Jarmo