JMP Wish List

JMP can’t handle billing project and data project levels (multi-level project querying) in Google Big Query.       Would like to be able to access multiple projects from within one Google Big Query DSN connection similar to what is offered by other products like Tableau or Power BI          ... View more

What inspired this wish list request? We extract data from a LIMS data base where we store both the average and individual data measured on a part.  The rows in the data table for the average contain 1 data point for every 3-6 of the individuals column.  We want to be able to connect the data points on the control chart without the chart looking strange where there are blank rows. Currently need to create a new batch number column for each parameter with a formula and value order in make the chart 'pretty'.      What is the improvement you would like to see?  Currently get this Add a formula column (for each parameter) to achieve this       Why is this idea important?      ... View more

The shape files for a Map Shape can be in any directory, but for a Background Maps they've got to be in Program Files\JMP\....\Maps. This directory is often admin protected, and sharing files means making hard copies per PC.   Allowing the user to specify a different directory (Maps folder remaining as default location) in the JSL would be great. ... View more

☐ cool new feature ☐ could help many users! [disabled: Query Builder is not used very often, right?] ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it       What inspired this wish list request?  https://community.jmp.com/t5/Discussions/Why-is-there-such-unexpected-re-calculation-of-columns-without/m-p/906944      What is the improvement you would like to see?  Something like the options in Tables/Subset:   At least: there should be a warning message like: you are using column formulas with reference to other rows. It's very likely that the result of this Query Builder is wrong. Please take case to disable the formulas - or remove them.   Why is this idea important?  The interplay of Query Builder and Formula Columns can be toxic. The new feature will save users from creating wrong results. The existence of the options will help the user.     other wishes from    ... View more

What inspired this wish list request? Playing with the edit pane to look at cells with large amounts of text. Created a formula to trim some of that text and then realized I couldn't highlight / copy text from the edit pane for the formula column.     What is the improvement you would like to see? I think the edit pane at the bottom of tables in JMP19 should allow text to be copied even if the cell can't be edited (as in a formula)     Why is this idea important? Even if a cell can't be edited, a selection of the contents of the cell should be able to be copied. When clicking a cell in the main table, I can see why, previously, this wasn't reliable -- especially if the rows weren't widened to see all the text. With the new edit pane making the full text easily accessible, being able to copy from within that pane would be another super improvement on some of already great JMP 19 table improvements.     ... View more

As a heavy user of JMP, I often work with multiple variables displayed on the same axis in Graph Builder. For example, when axis titles are like  ID 2 / THICKNESS 1 / THICKNESS 2 / TIME / ID , due to multiple variables being stacked or grouped, it becomes visually difficult to interpret which tick label belongs to which variable. I would like the ability to color both the tick label font and the tick label area (the region between the axis title and the plot) based on the variable. This would greatly improve readability and help users quickly distinguish between variables in complex visualizations.   ... View more

☐ cool new feature ☑ could help many users! ☑removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  In general, Jmp doesn't distinguish between upper and lower case - and Jmp ignores white spaces in Symbol names. So, :age can refer to the same column as :A G E  But :age and  :A G E can be also different columns. check if column exists?    JSL ignores white-spacing for names, most people don't take advantage of this!    Let's take the Concatenate platform as an example. This platform is very picky with column names. If Table A has a column :age and table B has a column :A G E,the combined table will contain 2 columns! In general this is a nice feature: better split the columns, the user can merge them later.   But for user who lived the carefree life of "difference don't matter" - the first collision with Concatenate can be traumatic.   What is the improvement you would like to see?  In Concatenate (and other platforms?) please provide an option "Column Names: Exact match". If the option is on, Concatenate is as picky as now, if it's off, Concatenate follows the usual rules of JMP/JSL when comparing column names.   Why is this idea important?  - The option will give the user more possibilities.   - The presence of the option will generate awareness!   - The idea is related to the option Exact Match (1 |0) of   dt << has column(), which will be introduced with Jmp18: data table : message column exists(colname)?    more wishes by   ... View more

☐ cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  I want to clean up a data table with a few hundred columns. A few columns are used in formulas and have to be replaced by new columns. The remaining columns can be deleted. When deleting the old columns, it is difficult to identify the columns which are used in column formulas.   What is the improvement you would like to see?  1) Please display a symbol next to columns that are used in Formulas.   2) Please provide a functionality to generate a formula lookup map. a) The map should list all formula columns with the columns used in the respective formula. b) In addition the Window should provide a list of all columns which are used in any Formula column.   e.g.    ratio = height / weight myequation= (height - weight)^sex   a) - ratio: height, weight - myequation: height, weight , sex   b)  - height - weight - sex   Part a) is useful to get an overview and to work on specific formulas,  Part b) is useful for batch-replace:  A right click menu should be available which allows to replace the specific column in ALL column formulas with a replacement column.   Why is this idea important?  Will help to edit column formulas after changes of the input column names.   more wishes by   ... View more

I don't have a lot of faith in the 'plot residuals by normal quantiles' for doing model diagnostics. I have typically saved the residuals from the model to a new column, then used the Distribution platform to create a normal quantile plot there.   The fit of the solid red line does not seem to match up well with where the residuals fall using Fit Least Squares. The slope of the solid red line is not a good fit. I looked at a few sample data sets and saw issues with the default model scripts in these data sets:   2x3x4 factorial Bounce data Wine data Below is a plot of the 2x3x4 factorial Residual Normal Quantile Plot. I've been told that the slope of the solid red line is based on the RMSE of 2.02.     If I save the residuals to a new column and regenerate the Normal Quantile Plot from the Distribution plot, the line is based on the standard deviation of the Residual Y column of 1.03. It looks like a much more sensible fit from a model diagnostics perspective.   Is this something that can be updated in future versions of JMP? Note that when you use Fit Mixed, the results in the Residual Plots there match my desired result from manually saving the residuals to a new column. ... View more

☐ cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it     What inspired this wish list request?  It's great that there is a list of "builtin" presets in the Format Pattern dialog. Unfortunately, some of our files use  2-3 additional formats which are not in the list.   What is the improvement you would like to see?  Please provide an option to store the current pattern to  "user defined" in the list of presets.   Why is this idea important?  Once a user encountered a format pattern that is not in the list  it is very likely that he will see it again and again - especially when loading the same type of data. Then it could help a lot if the user could specify the special patterns on the first encounter and all the other times: just pick the stored pattern from the list. more wishes by   ... View more

What inspired this wish list request?  ☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2023 (either this one or Tables join: option to update main table ) we have a workaround -> we don't need it anymore   Tables Update is a really nice Platfrom which can be used to merge columns into a data table or to update columns with the data from another data table. But sometimes the user has to wait for a long time till Jmp finishes a data table update - even with medium large data tables.   Sometimes, Jmp already gets stuck while editing settings in the Update GUI. Then it seems that Jmp crashed - , but after some minutes (or sometimes:  hours), Jmp finishes the calculation for the data preview and gives the user again the chance to edit the settings. It's clear that it takes a while to match hundreds of thousands of values in one table with values in another table. But I am surprised that merging two columns takes twice as long as merging one column Is the matching step triggered again for each column that is merged - or is it actually the sorting of the values which takes so long?   Often, I don't have unique identifiers in the source table: a single match value shows up several times in a column - with identical values also in the column to be merged. In this case, I wonder if the value of the first match is entered to the target data table, then replaced by the second  - and so on ... This could be accelerated by searching the last matching value in the source table - and just inserting this value.   A big drawback of the Update Platform: It starts with add columns and replace columns activated. If a table has e.g. 1000 columns, it takes a while till all columns are added to the preview window. The issue scales with rows_main     x     rows_2nd    x    columns_2nd. And as stupid as I am, I often start by defining the match columns ... which allows me to go for a long walk till I am allowed to pick the (1-2) column(s) I actually want to add to the table. There is a functionality which disables the preview if the table is too large. But I fear that the function just checks the length of the table -  and not the number of columns. Or the threshold is too large?   Please share your experience - how often you had to fill the time till your Jmp session was back again after an update of the preview tab.   Another issue is the Recall Button (addressed here: Disable Preview while filling the GUI via Recall  ) After clicking on Recall, the Update menu is filled with the saved settings - and after each change of a GUI setting there seems to be an update of the preview tab. So if you want to join large data tables - even if you just want to add a singe column - don't dare to press Recall ... before you disable the preview.   What is the improvement you would like to see?  Could you please improve the performance of Tables/Update.   Why is this idea important?  Tables/Update is a wonderful function. The Preview Tab is amazingly useful, I don't want to work without it. But I'm starting to get paranoia - how long will it take the next time when I try to add columns to a data tables. ... View more

What inspired this wish list request? Need to be able to match background color in Graph Builder to certain value in gradient legend.     What is the improvement you would like to see? Add ability to use an eyedropper to sample a color from within or outside of JMP and be able to set that color for lines or background.     Why is this idea important? Further flexibility in visualization capabilities.   ... View more

What inspired this wish list request?  Depending what you are doing in JMP, you sometimes have to unnecessarily move from wide data to tall data due to how column switcher / local data filter work - we cannot "filter" columns currently. This is one of the reasons why I did create Enhanced Sankey Plot (ESP) add-in as it is fairly difficult to quickly add/remove specific columns from graph builder.   What is the improvement you would like to see?  I would like to have new tool? "Column Filter" which would allow me to determine which columns I want to show. This would function basically like Data Filter but for columns. If I have a situation like this where I have multiple columns in my Y-axis for example I don't have any easy options to hide or add extra columns. If I want to some of those columns or add new ones, I have to stack the data first and the create a graph with local data filter This does work great but sometimes this feels very unnecessary step.   Why is this idea important?  This would make the gap between tall/stacked and wide/split data smaller. ... View more

I have sets of xy data measured on a part.  There are data points for "nominal" (ex: as designed location) as well as actual (where we measured).  If both PAIRS of data are plotted in JMP (using the trapezoid landing zone to add 2nd series on each axis), it gives 4 series as outputs - Xnom, Ynom - GOOD Xnom, Yactual - this is nonsense Xactual, Ynom - this is nonsense Xactual, Yactual - GOOD   I would like an option to have Y values tied to a set of X values so that only the GOOD (real) pairs plot on the chart. Comparison - in Excel, I would "paste special" a new set of data with both an X and Y column, and it asks if I would like to make it a new series and if I would like to define new x values for this new series.   Another typical instance where this is helpful is plotting Pi data.  The tags often don't have matching time stamps, but I want to see them together on the same chart.  Forcing matching time stamps can skew some data sets depending on how it is captured.  (I haven't used the new Pi import in JMP - I was working with Pi data pasted from Excel - just another recent example for me where I had many Xs that went to specific Y series and they weren't the same.)   This is an ease of use issue.  The work around is to stack the data so X and Y are all in the same column, with a label field that defines the series.  This can work for some data sets, but it is harder for many users to wrap their mind around or to know how to do.  This is a rare time I leave JMP and go back to Excel to plot a graph.   Example - bad graph (this is made up data as I can't share real data).  The "nonsense" series are * markers     Example of what a graph could look like (I made "nonsense" series a white tiny marker so they don't show):   ... View more

What inspired this wish list request? Writing scripts and finally this post How to supress script dump in log upon closing a chart?    What is the improvement you would like to see? 1. Message / argument to prevent report snapshot from single report I would like to see a message we can use to prevent a platform from being recorded when it is being closed which we could use when scripting. The message could be something similar as the preference we have   << Report Snapshot On Close(0) and of course it should be possible to use this as an argument in JMP Platforms.     2. A function which would change how snapshot behaves in current script Being able to disable all snapshots created from a script could also be useful. The setting could work in similar manner as Names Default To Here(1); and maybe it could be called something like   Disable Snapshot On Close(1);     Why is this idea important?  When writing and using custom scripts it can get quite annoying when your log is being spammed with report snapshots. This can be already prevented by modifying preferences but I would like to keep preferences as they are as I like that snapshots are saved when I'm using JMP interactively and just prevent these snapshots from my scripts. There is also at least one workaround which works from time to time but this is very clunky to start adding to every report Names Default To Here(1); dt = open("$SAMPLE_DATA/Big Class.jmp"); nw = New Window("", gb = dt << Graph Builder( Variables(X(:weight), Y(:height), Overlay(:sex)), Elements(Points(X, Y, Legend(9)), Line Of Fit(X, Y, Legend(11))) )); nw << on close( gb << close window; );   ... View more

What inspired this wish list request? After contacting JMP support regarding Bug when using combination of set each value, tables with same column name(s) and col statistical functions within a loop (00049239) I got to know that the way I have been using << Set Each Value and Col statistical functions (such as Col Rank() and Col Sum()) successfully for many years are unintended. The inspiration here is that the way they currently work make scripting in JMP much much faster and easier when creating new columns and if the behaviours were to change, I would have to rewrite all my scripts (most likely I will just start using something like Python at that point for all my data manipulation scripting needs).   What is the improvement you would like to see? Change the behaviour where user can use << Set Each Value with formula expression as  supported behaviour. Change the behaviour where expressions can be used as first argument (or any argument?) in Col statistical functions  as supported behaviour. Or at least provide confirmation that the behaviour won't be changing.   Why is this idea important? There are hundreds or thousands of examples in JMP community where these functions/messages are being used wrong. I use them wrong in almost all of my scripts as those behaviours are so powerful and much faster than any other options I know of in JMP. If these are to change without any notice (or even with notice) I will have to stay with some older version of JMP which still support these behaviours or start using other means for my data manipulation tasks.   Some examples from community: First Value for a Unique ID , How to calculate relativ values based on a position of a base value? , Special Formula Columns , Searching Maximum value of each row across several column and name of source column , Fill column with values based on another column with keys and associative array , JSL Companion 2nd Edition Applications of the JMP Scripting Language, Second Edition contains examples of using << Set Each value (for example 3_CreateDeleteColumns.jsl) ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  Freq and Weight can have different effects.   Jmp documentation makes it difficult to understand the differences: https://www.jmp.com/support/help/en/17.0/index.shtml#page/jmp/summary-launch-window.shtml#ww272136    SAS provides an application note  Distinction between the WEIGHT and FREQ statements  and an explanatory article about the differences: The difference between frequencies and weights in regression analysis    Jmp uses Freq differently from SAS: https://community.jmp.com/t5/Discussions/Not-sure-how-to-use-amp-quot-Weight-amp-quot-in-amp-quot-Analyze/m-p/684790/highlight/true#M87072      If the user wants to weight different values differently in a Median calculation (weights: 0-1), he has to use Freq: https://community.jmp.com/t5/Discussions/Not-sure-how-to-use-amp-quot-Weight-amp-quot-in-amp-quot-Analyze/m-p/684839/highlight/true#M87083  ...  and he is allowed to use Freq (in Jmp)   What is the improvement you would like to see?  Please add some explanatory text to the documentation - perhaps: some simple example which explains the difference between Weight and Freq and guides the user to pick the right one.   Why is this idea important?  To generate meaningful analysis a user has to understands the meaning of entries in the GUI. Best: via documentation - not via trial and error :)         more wishes submitted by   ... View more

What inspired this wish list request?  I use more than 2 spec limits per process parameter.   What is the improvement you would like to see?  Please allow more than one limit per side in spec limits, also option to customize the limit name/label will be much appreciated.   Why is this idea important?    I would like to see the following options when inserting spec limits: LSL2: xxx     Label(optional): xxx LSL1: xxx     Label(optional): xxx Target: xxx     Label(optional): xxx USL1: xxx     Label(optional): xxx USL2: xxx     Label(optional): xxx   ... View more

What inspired this wish list request?  I've experienced migrating scripts & add-in from JMP 15 to JMP 16 to JMP 17 which consume a lot of my engineering time to debug. We never know how many more versions JMP plan to release in the future. I foresee we will keep repeating this process, which really holding us back to fully automate the decision-making flow in operation. Imagine, if I have 10 scripts saved at 5 computers for machine learning which may contain >100 lines of code. Every time JMP release new version that is not compatible with old versions, I need to re-edit my scripts & test at all computers to ensure no disruption to the operation.   What is the improvement you would like to see?  -Create "add-in script converter" between versions. Maybe start with JMP 17 --> if user want to upgrade to JMP 18 license, this feature propose a new script or verify the old version code to see if it compatible.  -Maybe add this feature in "add-in manager" feature highlighted by other users. https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/ta-p/43736#U43736 https://community.jmp.com/t5/JMP-Wish-List/Integrate-Add-In-Manager-in-Jmp/idi-p/575114     Why is this idea important?  1. We can save a lot of time & do something else in JMP rather than keep re-edit our released scripts. 2. Easy for me to justify investment to buy more JMP license.   ... View more