JMP Wish List

This would fall under a small "quality of life" improvement but the legend for a stacked bar chart is always in the opposite order of what one would intuitively expect when going scanning from top to bottom (the top item in the legend is the bottom item in the stacked bar) . If that isn't changed it would be nice to have a "reverse" order button in the legend settings box, similar to what is available when changing the Value Ordering property for a column. ... View more

We miss one useful function for comparison all columns of two data tables in JMP16.       This helpful function was available in JMP15 to find easily unmatched columns (name changes of columns, additional columns and missing columns). Result was available in two seconds independent of number of columns. In JMP16 we have to manually scroll through all columns to determine if there are linked or unlinked (match). That`s why it takes more time dependent on number of columns and has a high risk to overlook differences. Is there a chance to get this function back in JMP16? ... View more

Hello,   I'd like to request support for overlaying multiple distributions (i.e., when separated by the "By" grouping) to compare them on the same plot. Thank you. ... View more

Would like to have the ability to actually hide rows that are selected to be hidden.  Makes review of specific rows quick.  Otherwise will just keep using Excel. ... View more

If I am including a script include("child.jsl") and the child has an error in it  x = aaa; I get a nice error output Name Unresolved: aaa in access or evaluation of 'aaa' , aaa/*###*/ at line 6 in some\path\child.jsl But if the error is a syntax error x = {"f", "d", }; // has an extra comma then I don't get the information of where the error is located Unexpected "}". Trying to parse operand for "List" operator. Line 5 Column 16: x = {"f", "d", ►}; I think it would be great if it told the file that is causing the error like a code error does.     This  becomes even more apparently a problem if the include is  x = { "f", "d", }; Because then I get a very vague error message Unexpected "}". Trying to parse operand for "List" operator. Line 8 Column 1: ►}; ... View more

In the histograms embedded in the data table (JMP 15 novelty), it would be great to have specification limits shown as well when they are defined in the column properties. ... View more

We get frustrated when we find JMP frozen after starting a script that takes a long time. But even in most such situations, only one CPU thread is active. JMP should be able to take advantage of today's multicore processors and keep working even while a heavy script is running. ... View more

As described in this discussion thread, it would be helpful if it were possible to use Graph Builder to plot data points that are "Excluded" but not "Hidden".   Currently, if data is not "Excluded" then it affects statistics that are plotted in Graph Builder. But if data is "Excluded" then it is also "Hidden" automatically (despite some confusing references in the JMP manual in a few places mentioned in the discussion thread).   Ideally, "Hide" and "Exclude" would operate independently in Graph Builder, as one would expect—and as it operates within other JMP platforms. ... View more

JMP currently does not have the capability of complex survey analysis. In sas survey analysis is done using several Proc survery___ procedures (surveymeans, surveyfreq, surveylogistic, surveyreg, surveyphreg) and I wish that JMP had such capabilities at least in future. These should take into account complex survey design including several stratums, clusters, and weights. ... View more

What inspired this wish list request? I was told that JMP is working on such a connector, and want to advocate for as accelerated development as possible. Our organization uses Databricks as our primary data platform, and connecting JMP to Databricks currently requires configuring the Simba Spark ODBC driver manually for each user. This process involves downloading and installing the driver, locating workspace-specific server hostname and HTTP path values, configuring DSNs through the Windows ODBC Data Source Administrator, and managing personal access token authentication — all before a user can run their first query. For analysts and scientists who aren't IT-savvy, this is a significant barrier. Any change to the Databricks workspace (cluster changes, token expiration, workspace migration) requires users to repeat or troubleshoot the process. The overhead of supporting this setup across a team is substantial and ongoing. What is the improvement you would like to see?  A native Databricks connector in JMP that allows users to authenticate directly using their existing Databricks credentials (personal access token or, ideally, Entra). The connector should: Present a simple connection dialog where the user enters their Databricks workspace URL and authenticates Automatically discover available catalogs, schemas, and tables based on the user's Unity Catalog permissions Respect existing Unity Catalog row/column-level security and access controls without any additional configuration Store connection profiles so users can reconnect with one click Support both interactive SQL queries and table import workflows within JMP Why is this idea important?  Will increase efficiencies and reduce complexity for end users.  Reduce IT support to help users connect, manage access tokens, and document lengthy checklists to guide users.  From a data governance perspective, honoring the Unity Catalog permissions would ensure that access controls are respected and still able to be centrally managed.       ... View more

What inspired this wish list request?  In formulation and similar fields, experiments often involve both mixture components and process factors. For standard numeric DOEs, JMP offers RSM models as a default, making DoE planning and model selection easy. However, for combined mixture/process designs, the equivalent—KCV models—are not included as a default option. Users must manually select and enter all relevant effects, which is time-consuming and error-prone. What is the improvement you would like to see?  Add “KCV Model” as a default model complexity option in JMP’s DOE planning and model selection, just like RSM for "standard" factors. This would let users select KCV directly, with JMP automatically generating the correct model terms—no manual effect selection needed. KCV models would then serve as the default for mixture/process combinations, just as RSM models do for numeric factors.   Why is this idea important?  Automating KCV model setup would save time, reduce errors, and make DOE planning much easier for users working with mixtures and process factors. It would provide a practical, balanced modeling option that’s especially valuable in formulation, but also useful in any area where mixture and process variables interact. ... View more

What inspired this wish list request? the functionality to Edit a table script with double-click, and Paste a table script with Ctrl+v was removed in JMP 19.    What is the improvement you would like to see? Put it back the way it was     Why is this idea important? This is core functionality that has been part of my workflow for many years. The new workflow is cumbersome and keeps me from focusing on what I'm working on to spend unnecessary time trying to figure out how to do what was once second nature.     ... View more

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

In Fit Life by X currently only sigma = 1/beta is reported in the Weibull results (see Devalt example data below). For users familiar with the Life Distribution platform who then start using Fit Life by X, this makes it hard to read and to compare. With the Weibull distribution everybody's looking for a beta.   If you could add a hint that exp(mu) = Weibull alpha, that would also be very helpful.       ... View more

In the Predictive Modeling platform, it would be nice to have options, similar to the alternative confusion matrix cutoffs, to change various tuning parameters for a number of iterative steps of values. For example, in a partition, vary the minimum split size between 3 and 10 in increments of 1 (similarly for the other paramters). I realize this is not difficult to accomplish with a loop in a script, but it would be nice if it was as easy as with the confusion matrix cutoff example, or the way it works to put a variable in the By box when doing an analysis. It would then be easy to examine how various performance measures change as the tuning parameters vary. It has been my experience that most of the default parameters in JMP work quite well, but it becomes tedious to test whether or not this is true. This suggestion would automate this testing and make it easier to determine whether or not to override the defaults. ... View more

Support,   I found a way to create a vlookup through scripting in JSL, but is there a possibility to include something like this in the formula editor under the Comparison menu?   Thanks for your consideration to this idea.   Ana Maria Heilman-Morales ... View more

I'd like to be able to drag something out of a project much like a Chrome Tab.   ... View more

For each version of JMP, having to turn on in preferences the VIF column for Parameter Estimates in Fit Least Squares. I teach the Regression class in JMP, and always have to show new users that you have to right-click over Parameter Estimates table in the report to select VIF from the columns that are not displayed by default. I then have to show the class how to turn this on in the Preferences. One suggestion would be to allow this to be shown with a drop down menu item. From the Least Squares Fit Inverted Red Triangle:    Under menu item Regression Reports, the Parameter Estimates can be turned on or off. (on by default)    But also under this menu, selecting the "Show All Confidence Limits" turns these two columns on in Parameter Estimates, and in Expanded Estimates (but not a column available in Sorted Estimates). So can "Show VIF" be added to this menu just like "Show All Confidence Limits"? It would be easier to find instead of hidden in a right-click on the table in the report. Saw this question a couple of times in JMP community as well. Wish list for JMP15. ... View more

I wish JMP could easily open data from or save data to Google Sheets, including passing credentials and scriptably.  I recently did learn how to do this by using JSL to call R and use the package googlesheets but would be nice to have a built-in solution for this ... View more