JMP Wish List

GemmaBarnes · ‎06-06-2023

What inspired this wish list request? Currently, within the Concatenate function, columns to be concatenated have to have exactly the same header (including case). Frequently, there are small differences or typos which JMP interprets as being a different column. This can be rather frustrating and slows things down. What is the improvement you would like to see? The concatenate function to have an extra window where the user can state which columns are matches for each other (I'm thinking it could be something similar to the Group function within Recode)- for each file you're concatenating you could have a list of columns and you could select your columns to match and click a "match" button. If JMP could suggest matches (and show its suggested matches) before producing the new data table that would be useful too (and help catch the odd typo) Why is this idea important? It smooths out the Concatenate process and saves you time instead of having to change all your column headers to exactly match.

StarfruitBob · ‎05-22-2023

What inspired this wish list request? Multiple file import and open functions are able to save a list of files they open in a list. I'd like to see something similar with functions that can generate multiple columns from one, mainly text to columns What is the improvement you would like to see? saving text to column to a variable saves a list of column names generated to a list. Example: A dt containing a column of numbers separated by commas new_cols_list = dt << Text to Columns( columns( :Numbers column ), Delimiters( "," ) ); Why is this idea important? This would allow more compact identification of generated columns, and therefore more streamlined, and less error-prone way of working with these columns, if needed

hogi · ‎03-23-2023

What inspired this wish list request? The Filter menu in the column list is very useful. The user just has to add tiny identifiers to the column names to get a handle to select a set of columns (much more flexible that grouping :). For larger data tables, it could help to have an automatic way to add strings to column names. What is possible at the moment: - use JSL: https://community.jmp.com/t5/Discussions/Append-a-string-to-column-names/m-p/614825/highlight/true#M81470 - use Rename Columns from the Jmp Scripting tools Add-In: https://community.jmp.com/t5/Discussions/Append-a-string-to-column-names/m-p/614760/highlight/true#M81465 Unfortunately, the two approaches are not recorded in Workflow Builder. The user has to script on his own. @Jed_Campbell found a very creative way to achieve the task with steps which are recorder by Workflow Builder: https://community.jmp.com/t5/Discussions/Append-a-string-to-column-names/m-p/614826/highlight/true#M81471 This is can be seen as a proof that "actually it is possible" - but less as a viable way which you would suggest your colleagues after 2 weeks with Jmp. So, under the line, at the moment there is no easy way to achieve the task. What is the improvement you would like to see? Please steal some ideas from Scripting Tools /Rename Columns and add them to std. Jmp. especially: A similar option could also be added to the Recode function -. Why is this idea important? It's not - just an improvement of Jmp which will help the users to change column names and entries in a more flexible way. more wishes submitted by

hogi · ‎03-08-2023

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it What inspired this wish list request? The Recall buttons in the GUIs of the standard platforms are great. Such a help to work efficiently! Sometimes, I have to toggle between two settings or need to trigger an action that is similar to a step that I did some while ago: Total Recall - or Back to the Future? how to travel further into the past What is the improvement you would like to see? Please add a history to the recall function. If the current implementation of the save and recall function saves recalls settings to/from an associative array of settings, the new version should save and recall the settings to/from a list of associative arrays. With a mouse click on the button, the user can trigger the standard recall of the last setting. By right clicking (or shift/CTRL ...anything) clicking a context menu should show up with numbers - 1 to -N. Clicking on Number -M should trigger a recall of setting # -M. Why is this idea important? A history will make the recall function even more versatile :) more wishes submitted by

hogi · ‎03-04-2023

What inspired this wish list request? While waiting for a universal update tool (Join, Concat and Update - JMP User Community), it's already great so have now with Jmp 17 a Preview Area in the Tables - Update Platform. This functionality helps a lot to check and adjust the setting "on the fly". What is the improvement you would like to see? Please implement a functionality in the Preview area. - highlight added columns - highlight columns with changes (the amount of changes could be indicated with different color intensities) - highlight changed entries Why is this idea important? The preview is already great. Thanks to the development team - wonderful idea! But it's still a bit dangerous. The columns in the main table look exactly the same - no matter if there were changes or not. A user who wants to add some specific columns could ignore the Replace part. This is particularly dangerous as the default setting or Replace is "All" - so kind of: biggest harm possible for any unexperienced user you didn't care. Highlighting the newly added Columns will help in addition to better see the changes. more wishes submitted by

nao · ‎12-23-2022

Problem When JMP imports data, e.g., a CSV or an XLSX file, JMP guesses the appropriate Data Type and Modeling Type for each Column. This guess is helpful but is not (cannot be) perfect for every scenario. When a large table, e.g., one with hundreds of Columns, is imported, subtle imperfection of the guessing may lead to a lot of repetitive manual work afterwords. Specifically, JMP treats all Numeric Columns as Continuous. Suggestion I believe many users will benefit if some simple rule-based branching is added here. A specific example of such rules can be adding an option to treat Columns which contains only integers contains only a small number, e.g, 10 or less, of unique values as Nominal. I believe this applies to all recent versions, e.g., 14, 15, 16, and 17.

hogi · ‎12-09-2022

☑ cool new feature ☐ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it In the Table summary menu, for tables with modeling type multiple response, please provide a checkbox to use/not use the multiple response. At the moment, the below code generates a summary table like this: such a table could make sense /how many students have 2 and more sports activities?) But with the checkbox, the user could decide if he perfers the first table or a summary table which analyzeds and groups the multiple response entries (like GraphBuilder would do in Jmp 17): On the other hand: I am quite happy that Summarylists multiple response columns (although it doesn't use the information). [much worse: tabulate doesn't even list such columns: https://community.jmp.com/t5/JMP-Wish-List/enable-quot-tabulate-quot-support-for-columns-with-modeling-type/idi-p/557686] Names Default To Here( 1 ); dt = Open( "$SAMPLE_DATA/Big Class.jmp" ); New Column( "sports", Character, "Multiple Response", Set Selected, Set Values( {"", "running", "", "tennis", "tennis", "tennis, football", "tennis, running", "", "", "football", "running", "", "tennis", "", "football", "running", "tennis", "", "", "tennis", "", "football, running", "running", "running", "running", "running", "", "tennis", "", "football", "football", "tennis, football, running", "football", "tennis, football", "running", "", "", "", "football", ""} ) ); Data Table( "Big Class" ) << Summary( Group( :sex ), N, Subgroup( :sports ), Freq( "None" ), Weight( "None" ) ); more wishes submitted by

hogi · ‎09-12-2022

☐ cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it If columns with type "character" are selected, the New Formula Column menu shows the submenu character. Among other option, there is the function concatenate which concatenates the strings. There are also 2 more functions. They concatenate with Space or comma. My wish: A more general function "concatenate with string ...". The idea: After selecting this function, a window pops up and asks the user to enter a string. Then one can concatenate also with "_" or "-" or ... Contrary to what I wrote in a previous version of this post, "concatenate" is also available if characters AND numbers are selected. If numbers are selected as well, a char(number) is added automatically. Cool :) Unfortunately, the character/concatenate function is missing if all the selected columns are numbers. Could you please make the concatenate function available also for this variant? more wishes submitted by

john_madden · ‎01-17-2018

Would like a new column property (analagous to Range Check and List Check) for character columns. It would (interactively) validate column input against a pattern specified as a regex or as a search string, and reject input that failed to match the desired pattern. My purpose is to make it less error-prone when manually filling out tables with data like id's, names, etc. that are supposed to conform to a know pattern.

AvigdorC · ‎12-09-2017

In Fit Model reports, show next to each LS Mean, the actual number of observations used to calculate it (as the "Number" next to each mean in "Fit y by X"). This information is especially important when the model is re-analyzed (often several times) after suspected outlier data point(s) is/are excluded or un-excluded.

shampton82 · ‎02-09-2022

Hello JMP team, I'd like to suggest the following for the column options: On the columns list located on the left side of a data table, can you add the options for standardized attribute, column properties, formula, recode, and new formula column when you right click on the column? On the main column titles, can you make it so that by clicking on the column and holing the alt key that it will move that column into view on the column list at the left of the datatable? On the columns list located on the left side of a data table, can you add an option to filter by modeling and data type? Thanks for considering these options. Steve

Fulcrum · ‎10-21-2021

Missing data is a common problem with data analysis. I would like JMP to include the option to perform multiple imputation on data with missing values. Currently I am sure many of us are restricted to options like R when it comes to performing such functiions on data and this option in JMP would only serve to make JMP the all-in-one data analysis solution which it is gaining a growing reputation for.

reese_sj · ‎02-08-2021

It would be useful to be able to recode column names, but only ones that are selected. Often with larger data sets there is only a subset of columns that need to be modified or there is a variety of naming conventions used. In these cases being able to recode a subset would allow for more customization with the recode tool.

txnelson · ‎03-07-2020

I would like to right mouse click on a rowstate column and have an option to select matching "colors" or "Markers" or "Colors and Markers"

reese_sj · ‎09-17-2019

During the curation phase of a text exploration, it would be beneficial to be able to recode recoded words or phrases. The process of curation typically involves cleaning up the data, exploring the results, and then determining if another round of curation is necessary. Often times there are cumulative recodes that are necessary to get the context included into a term or phrase. For example, first I need to recode and group the terms Smelled and Smelling into Smells. Then I can find phrases of Smells Good or Smells Bad and so I would Add phrases to my term list. However, there are multiple variations of these phrases and if any of the phrases include a term that is already recoded, then the phrase can no longer be modified (even though the newly recoded phrase will show up in the Recoded term list). So I would no longer be able to modify Smelled Good and Smelling Good into a new phrase, "All Smells good phrases". An example can be seen with the sample Pet Survey. Steps: Analyze > Text Explorer Select all terms > Recode Group similar values > OK Select a few phrases such as Dogs Bark and Dogs Food Add phrase Term list Select the 2 added phrases Recode >Group these 2 phrases and give them a new Name (to make it easy to find) such as "Dog stuff" Not all phrases will be recoded (although a peek at the Managed Recodes will show that this change has been made). In this example it might not make sense to make "Dog stuff" but I am trying to show the issue. An actual example might include perfume comments. Imagine I first need to recode all related synonyms (Scent, scents, smell, smells, smelled, odor, fragrance....ect). Next I want to add phrases that provide some context such as Good scent, Great smell, Amazing perfume and recode the phrases into a Positive Scent or a Negative Scent group. This is where the recode evolution would be useful.

txnelson · ‎02-20-2019

I would like to see the Row State column to have multiple row state settings available at the same time. Such that Platforms that are run against the data table would be allowed to select which row state copy it should use. Use Cases Open the Big Class data table, run twice Bivariate using height by weight. Color the data points in one chart based upon row state colors based on Sex, and the colors in the second Bivariate based upon the second row state settings where the colors are based upon age. Open multiple platforms. Set different platforms to different row state versions. Change the selections in a particular platform changes the display in only the platforms that have been set to use the same row state version. Open the Subset platform, and select which row state version to use for the selection of the rows to be copied to the new data table. The Link To Original needs to honor which row state version is associated to the selection when the subset was created.

gerd · ‎02-12-2019

It would be great if labels in Graph Builder could be more easily aligned, e.g. by a right-click -> Align Labels, or Align Selected Labels (alongside an invisible vertical or horizontal axis). If something like this already exists, please give me a hint... I often label e.g. two-dimensional outliers by their serial number, align labels to make them readable, resize the graph at some point, and then have to start over again (see the Hollywood Movies example below). Maybe it could be possible to group selected labels (e.g. after alignment) and then move them around as one group of labels. Or maybe after alignment, labels could be allocated their X and Y coordinates at that moment, and when resizing the graph, only font sizes for labels are adjusted for readability, but labels remain at their coordinates.

Chris_Rodrigues · ‎11-29-2018

In Graph Builder charts I frequently place text box annotations on top of the charts. When I add more charts, change the scale, or resize anything, I notice the annotation moves around and resizes itself automatically to try to stay where it thinks I want it to be. But I find that the annotation never ends up where I want it, so I have to go move it again manually anyway. Also, when the annotation text box resizes itself, it sometimes shrinks to a tiny sliver. The text is still visible, but it is impossible to click on it to resize it or delete it. I think the Text Box feature needs to be fixed so it never allows the text box to be shrunk to zero width or height. I would consider this a bug. After this happens it becomes impossible to change or remove the text boxes using the GUI; you basically have to start over and rebuild the graph. Of course, you always can "save script to data table" and then edit the script to remove the offending text boxes, but this is not very user-friendly. It would also be nice if we had an option to lock the size and position of a text box (or line, shape, etc...) so it does not move or resize with the chart underneath it.

hogi · ‎06-29-2024

☑ cool new feature ☐ could help many users! ☐ removes a bug ☐ nice to have ☐ nobody needs it What inspired this wish list request? Thanks for implementing the modeling type Vector for Columns with data type expression. Thanks for the aggregation options which are provided in the new formula column menu: What is the improvement you would like to see? Please add more options: - N (how many entries are in the vector) - N non missing - N unique - @ community: do you have further suggestions? Why is this idea important? the new options will make the modelling type Vector more useful. other wishes from

hogi · ‎05-15-2024

☐ cool new feature ☐ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it What inspired this wish list request? this community discussion : Graph Builder: Unclear statistics when using multiple response columns @gnu23 wrote: I think the discussion boils down to the question, if statistics on multiple response columns should generally either use the number of responses (standard now in JMP) or the number of rows as 'n'. In my opinion the second option would make more sense for many use cases and an option to switch between these two values for 'n' would increase the (already very nice) functionality of multiple response columns. The default statistics in Graph Builder for counts and percentage, is (*): "one row counts one - Ntotal (denominator for percentages) is the number of rows". [This statistics can be adjusted via the Freq/Weight drop zone.] Surprising: If a column with modeling type "multiple response" is used ANYWHERE in the graph, the statistics changes to "one response counts one [OK] Ntotal (denominator for percentages) is number of responses" [maybe: not OK]. So, to generate meaningful bar charts on the porcelain layer, it seems that on the plumbing layer Jmp stacks the individual responses, creating additional "rows", and then applies the standard logic (*) For simple bar charts, this might be reasonable, but for Ntotal and the calculated percentages it leads to funny/strange effects. What is the improvement you would like to see? Please provide a more meaningful statistics for Multiple Response (e.g. as an alternative to the current version): "one response counts one But: denominator for percentages (Ntotal) is the number of rows contributing to the plot - like in standard Graph Builder" on the plumbing layer one might think of: Any column with multiple responses is split into "indicator columns", representing each response - the number of rows stays constant. This approach is much closer to the default Statistics in Graph Builder. As a side effect, this alternative approach will also fix a bug which shows up if multiple columns with modelling type "multiple response" are used in one graph: https://community.jmp.com/t5/Discussions/Graph-Builder-Unclear-statistics-when-using-multiple-response/m-p/754313/highlight/true#M93647 Why is this idea important? a) Meaningful statistics. b) no misleading statistics anymore for users who don't "notice" other wishes from

JMP Wish List

Concatenate: column matching

saving list of cols created by text to column

Recode and Recode Column Names: apply for specific rows/columns

Recall: add a history functionality

Tables - Update: Highlighting changes

Numeric Nominal Columns on Import

Table summary: enable/disable multiple response

make NewFormulaColumn/Character more flexible

Pattern Check column property

Presenting actual number of observations for each LSMean in Fit Model

Column options

Multiple imputation

Recode Column Names- Only selected columns

Allow for "Select Matching Cells" for the rowstate column

JMP Recode request- how to recode previously recoded terms

Allow the Row State column to have multiple Row State settings

Label Alignment in Graph Builder

Lock Graph Annotation Size/Position

modeling type: vector - add N items

Graph Builder: Option for "statistics by row" - not by response