JMP Wish List

What inspired this wish list request?  Currently, JMP's (JMP Pro 19.0.0) built-in 4PL (Four Parameter Logistic) model uses an exponential function with base e, while our validated bioassay analysis software uses a 4PL model with base b = 2. Because of this difference, results from JMP cannot be directly compared with those generated by our validated workflow. Our team relies on validated software to calculate relative potencies and perform bioassay analyses. However, every action in the validated software is recorded in an audit trail, making exploratory analyses time consuming. For example, when investigating whether removing a specific dilution point from bioassay improves suitability criteria such as equivalence, parallelism, or R^2, each modification requires documentation and justification. JMP is an excellent environment for rapidly exploring data and understanding how changes affect assay performance. However, the inability to define a custom 4PL model using a different logarithmic base limits our ability to use JMP as a screening and exploratory tool while maintaining consistency with our validated calculations. What is the improvement you would like to see?  I would like JMP to support user-defined 4PL models, allowing users to specify the exponential/logarithmic base used in the curve-fitting equation (e.g., base 2 instead of the current base e implementation). In addition, it would be valuable if user-defined 4PL models could leverage the same bioassay functionality that is currently available for JMP's predefined models, including: Relative potency calculations Parallelism testing Equivalence testing Confidence interval estimation Combined relative potency calculation using homogeneity or heterogeneity testing Other bioassay suitability and comparability metrics Ideally, users could define a custom model formula within the Bioassay platform or through a scripting interface (JSL) and then apply the standard bioassay analysis workflow to that model. Example use case: Fit a custom 4PL model with base 2. Set and evaluate assay suitability criteria. Remove or include selected dilution points. Immediately observe the impact on relative potency estimates, confidence intervals, equivalence, parallelism, and goodness-of-fit metrics. Use the results for exploratory assessment before executing the formal analysis in validated software. Why is this idea important?  This idea could significantly improve JMP's value as a bioassay exploration and decision-support tool. It would provide: Consistency with validated workflows: Users could match the exact model specification used in validated software, increasing confidence when comparing results. Faster exploratory analysis: Scientists could rapidly investigate data quality issues, outliers, and alternative fitting scenarios without the burden associated with validated systems. Improved efficiency: Assessing the impact of data changes on relative potency, confidence intervals, equivalence, and parallelism could be performed in real time. Greater flexibility: Organizations using custom or default assay models would be able to use JMP without needing to compromise on their established model specifications. Adoption of JMP in regulated environments: JMP could serve as a powerful sandbox environment for evaluating assay behavior prior to formal analysis and reporting. ... View more

LearnBot Improvements Enhance LearnBot’s responses by leveraging content from the JMP Community, JMP YouTube channel, and the full JMP website knowledge base. Improve LearnBot’s support for the JSL by incorporating information and examples from the official JSL books and documentation. When LearnBot recommends external resources or websites, these links should open in a new browser tab or window instead of replacing the LearnBot session. Benefits Integrating this content into the underlying LLM knowledge base could significantly improve the quality, accuracy, and completeness of LearnBot’s answers. This would help provide more relevant guidance, richer examples, and better support for both JMP functionality and JSL programming. ... View more

What inspired this wish list request?  I spent a bunch of time debugging an issue with variable scope. If {default local} is used within a function (which I almost always do) then the function can't access global variables unless the scope is explicitly specified with :: (which I didn't know). However, Print() will silently go looking for itself even without the :: - and given that Print() is a pretty basic debugging tool, that gets very confusing! What is the improvement you would like to see?  Print() should behave the same in terms of variable scope as everything else Why is this idea important?  Current behaviour is illogical and inconsistent. JMP19.1.1. ... View more

What inspired this wish list request?  I have a bubble plot that I have to label and provide on a recurring basis.  I need the labels to automatically position themselves to they don't overlap though or even hide if there isn't room for them.  JMP doesn't have that functionality (and neither does Excel or Power BI).  However, R does, so that's what I'm forced to use. What is the improvement you would like to see?  This is the snippet of R code for my ggplot visual that creates the point labels without overlapping them. g1 = g1 + geom_text_repel( aes(color = !!input$color_by), # map color here! size = 3.5, # font size in the text labels min.segment.length = 0, # draw all line segments nudge_x = ifelse(g1$data[input$xvar] > 3, -0.2, 0.2), force = 10, force_pull = 1, box.padding = 0.3 ) It's extensively documented here:  https://r-graphics.org/RECIPE-SCATTER-LABELS.html Why is this idea important?  I create ad hoc analyses outside of R and JMP is my go-to platform for such things.  Unfortunately, labeling the points is terrible and is especially frustrating since I know it's possible in R.  This also feels like an intuitively important feature that could be used on many plot types, not just scatter. ... View more

What inspired this wish list request?  I have a bubble plot that I have to label and provide on a recurring basis.  I need the labels to automatically position themselves to they don't overlap though or even hide if there isn't room for them.  JMP doesn't have that functionality (and neither does Excel or Power BI).  However, R does, so that's what I'm forced to use.   What is the improvement you would like to see?  This is the snippet of R code for my ggplot visual that creates the point labels without overlapping them. g1 = g1 + geom_text_repel( aes(color = !!input$color_by), # map color here! size = 3.5, # font size in the text labels min.segment.length = 0, # draw all line segments nudge_x = ifelse(g1$data[input$xvar] > 3, -0.2, 0.2), force = 10, force_pull = 1, box.padding = 0.3 ) It's extensively documented here:  https://r-graphics.org/RECIPE-SCATTER-LABELS.html   Why is this idea important?  I create ad hoc analyses outside of R and JMP is my go-to platform for such things.  Unfortunately, labeling the points is terrible and is especially frustrating since I know it's possible in R.  This also feels like an intuitively important feature that could be used on many plot types, not just scatter.   ... View more

What inspired this wish list request? An inability to easily connect to a snowflake service account without a separate installation of the ODBC driver.     What is the improvement you would like to see? The baked in snowflake connector (or any REST data connector, for that matter) to be able to function using public/private key pairings for authentication.     Why is this idea important? Our service account for snowflake are public/private keys. And while ODBC setup can handle these key pairs, they also require additional setup of the driver, and depending how technical or how IT may have items locked down, can be more cumbersome for some users. Being able to use built in REST connector in JMP has been great when it was just un/pw authorization, but with it shifting to keys, I now need to go back to ODBC OR build a special python program to do the connection/querying work.   ... View more

What inspired this wish list request? I need to install Python packages in a custom directory on my machine (e.g., C:\lib_jmp_python ) using the standard Windows PYTHONUSERBASE environment variable. Currently, if I run jmputils.jpip('install', 'package_name') , my system variable is completely ignored. The jmputils.py script hardcodes the installation paths by forcing its own site.USER_BASE and overwriting the subprocess environment. This makes it impossible to route packages to a custom local folder using standard Python OS variables; everything is forced into the default JMP AppData/ProgramData directories.   What is the improvement you would like to see? I would like jmputils.py to respect the system's PYTHONUSERBASE variable if it is defined by the user, and only fall back to the default JMP paths if it is not set. Specifically, in the jpip() function, a simple conditional check could be added: if 'PYTHONUSERBASE' in os.environ: site.USER_BASE = os.environ['PYTHONUSERBASE'] elif site.USER_BASE is None: site.getuserbase() The exact same logic should be applied to the create_jpip() function when generating the jpip.bat script, replacing the currently hardcoded set PYTHONUSERBASE=%APPDATA%\JMP\JMP\Python with a dynamic check.   Why is this idea important? This is highly valuable for users and IT administrators who need strict control over their Python environments. It allows users to route potentially large Python packages to specific drives or custom directories without breaking JMP's isolated environment. Ultimately, it aligns JMP's Python integration with standard Python behaviors, reducing friction and confusion for developers trying to manage their packages efficiently. ... View more

What inspired this wish list request?  One of the biggest bottlenecks in using JMP is creating structured formatted output to use in technical reports and presentations.  The current best practices include either a lot of scripting, journaling, and/or copy/paste actions.   It would be nice to be able to define a report structure with elements from JMP outputs included at specific locations, along with formatted text.     What is the improvement you would like to see?  Markdown is a well established approach for simple general construction of formatted output.  I would like to see a "JMP Markdown" capability, where I can create a markdown document that includes formatted text, JMP output (specific graphs from a report, specific tables from a report, and specific values from a report) in defined locations in the document.  The output would be a markdown document which could then be converted to various formats particularly PDF, Word DOCX, and Powerpoint PPTX Potential Workflow: Create blank markdown In parallel/sequence: Create JMP analysis report Select output from analysis report (with selection tool) and insert placeholder from the output in the markdown document. Add text with formatting tags  Save markdown file Run markdown conversion to desired format A GUI to facilitate creating the markdown formatting would be nice, also.  WYSIWIG interface in the markdown document would also be nice.   I could see this also be something that could be published to JMP Live (by converting the markdown to HTML). Why is this idea important?  This would greatly improve the ability to create formatted output from JMP that meets the specific needs of the user without extensive copy/paste and editing.  It would also enable standardized reporting and automation of analysis all the way from data ingestion to final reporting.     ... View more

What inspired this wish list request?  When developing dashboards for JMP Live that contain large numbers of products with significantly different run rates, the visualizations can quickly become noisy and difficult to interpret. This is especially true when multiple products share the same equipment or manufacturing track. For example: Product A runs approximately 5 lots per week Product B runs approximately 79 lots per week Product C runs approximately 2 lots every 5 weeks All three products run on the same equipment track. While the dashboard correctly displays the full population of data, the large differences in run frequency can cause the higher-volume products to dominate the visualizations. This makes it difficult for users to focus on lower-volume products or perform targeted outlier analysis. Users often request the ability to isolate or filter specific product populations within the dashboard so they can investigate trends, anomalies, or performance issues without the noise from unrelated data. What is the improvement you would like to see?  An enhancement that would allow users to interactively select or filter subsets of data directly within a JMP Live dashboard would significantly improve usability. Ideally, this would include the ability to: Select specific regions of a graph (such as lasso or box selection) to dynamically filter the dataset Filter by product, equipment, or other categorical variables directly from the visualization Update all linked graphs in the dashboard based on the selected subset This type of interactive filtering would allow analysts to quickly narrow down to the most relevant population without needing to create multiple versions of the same dashboard.   Why is this idea important?  Interactive filtering would make dashboards more effective for both analysis and communication. Analysts could quickly isolate specific product populations for outlier investigations, while operational teams could view the data most relevant to their work. This would improve usability, reduce the need to create multiple dashboards for different product groups, and make it easier to communicate insights during pass-down discussions and team reviews. Overall, it would allow teams to work more efficiently with large and diverse manufacturing datasets.   ... View more

What inspired this wish list request?  There are often times when it would be nice to have units appear as we might write them by hand, e.g. g/cm 3 instead of g/cm^3, or even with some text as a subscript: sample BKG  , but JMP does not make this easy. In fact, they seem to have taken away the copy/paste feature where you could write the text in Word and then copy/paste it into JMP and the formatting would be brought over into JMP.   What is the improvement you would like to see?  I'd like to see JMP add this text editing capability into JMP (and into JSL in particular for customization).   Why is this idea important?  It's important because it helps to improve messaging to the "consumer". People like to see additional information as subscript or superscripts. No one likes to read smapleBKG or g/cm3, they want the improved visual cues that comes with being able to move ANY text to superscript or subscript.   ... View more

What inspired this wish list request?   At one time there was a nice add-in, Correlate Y by X Add-in that computed both the standard Pearsons correlation along with Non-Parametric fits.  It was very easy to engage and worked well.  However, that add-in has not worked on the newer versions of JMP.  It is very common to use the non-parametric rank and the Spearmans rho for many applications.       What is the improvement you would like to see?  Simply find a way to enable that add-in to work in JMP19    Why is this idea important?  Currently, the only way to access a non-parametric correlation to obtain a Spearmans rho value is the multivariate test platform.  That can work well if the number of variables is low.  But in many cases, the desire is to have a one by many correlation calculated.  And when the many are several hundred, the multivariate platform is simply inapproriate for that purpose.     ... View more

What inspired this wish list request?  Many times we need to identify specific points by color or by marker in our Graphs (diffetent Graphs - Variability/Control Chart/BoxPlot...) and we need to have a Table SubSet of this selection   What is the improvement you would like to see?  We would like to have the capability in the Table -> Subset to select data by color or by marker.   Why is this idea important?  We need to do it by simple menu... and not write any kind of  script: the script is not user-friendly and no scalable   ... View more

What inspired this wish list request?  I write scripts for process engineers to generate Control Charts for their products as part of their Trend Review process. I have begun to add buttons to the chart window so that the engineers can turn on/off certain features, such as activating/deactivating spec limits. Another helpful feature of control chart builder is the Phase option, especially if one wants to compare production across multiple lines. This is a feature I want the engineers to be able to toggle on/off in real time.   What is the improvement you would like to see?  I would like for the object message << Phase() or something similar to be added to JMP for Control Chart Builder so that code can be written that would activate/deactivate Phasing at the click of a button. Considering phasing can be manually activated/deactivated if the Control Panel window is open on the chart, this should be made possible using JSL so it can be done in the background without requiring any knowledge of how to do it.   Why is this idea important?  Our engineers do not have the time to become JMP experts. I want to be able to provide them with scripts that are as helpful and as versatile as possible, while being incredibly intuitive and simple to use. To do this, I need these features to be possible in JSL, preferably without re-launching the control chart builder platform entirely.    ... View more

What inspired this wish list request?  The current version of JMP available to us does not allow performing an Accuracy Profile (β‑expectation tolerance interval), which is a key statistical approach used in analytical method validation. As a result, it is currently difficult or not possible to properly assess total error by combining bias and precision in a single, regulatory‑accepted framework. Example use case: During validation of a quantitative analytical method (e.g. HPLC or bioanalytical assay), multiple measurements are generated across several concentration levels and analytical runs. Regulatory guidelines (such as SFSTP, EMA, or ICH Q2) recommend the use of the Accuracy Profile to demonstrate that the method is valid across the intended concentration range. With the current JMP version, these calculations and visualizations cannot be generated directly, requiring manual calculations or external tools, which are time‑consuming and prone to error.   What is the improvement you would like to see?  I would like to have access to a newer version of JMP that includes the built‑in Accuracy Profile platform, allowing users to: Compute β‑expectation tolerance intervals Visualize bias and uncertainty against acceptance limits Model intra‑ and inter‑series variability Automatically generate validation‑ready graphs and statistics   Why is this idea important?  This improvement is important because it directly supports regulatory compliance, data integrity, and efficiency. Value for users: Enables compliance with current analytical validation guidelines Reduces the risk of calculation or transcription errors Saves significant time compared with manual processing Improves confidence during audits and inspections Overall, having access to the Accuracy Profile in JMP is a must‑have capability for users involved in analytical method development and validation.   ... View more

What inspired this wish list request?  For general JSL programming, it would helpful if display boxes such as Outline Boxes, Table Boxes, Graph Boxes could have user/programmer defined properties assigned to the display box.     What is the improvement you would like to see?  Add the ability to assign properties to display boxes.  I propose something like the "Add Context("label", "value")" message that can be sent to Outline Boxes.  Perhaps an <<Add Property(key, value) or <<Add MetaData(key, value).  Make these properties retrievable using a JSL message like <<Get Property(key) or <<Get MetaData(key).   Why is this idea important?  This would create additional options for JSL programmers to develop reports that are more easily dynamic and controllable.  See, for example, https://community.jmp.com/t5/Discussions/close-all-like-this-user-defined-outlines/td-p/935787.     ... View more

What inspired this wish list request? Difficulties with workflow builder working when table/column changes take place (table not found, column not found, etc).     What is the improvement you would like to see? I would like to see workflow builder more inherently utilize variables. Both natively on the JMP backend as well as in the GUI for users. When I run a workflow or share a workflow and something like a tablename changes, JMP is very good about giving the user an opportunity to rectify the difference. However it's often unclear where in the process steps the change needs to be rectified so users, including myself, may opt to just stop the workflow to try a different avenue (wait, what was JMP expect that wasn't there, how do I fix it? etc). And when I go to see what happens, maybe I see something in error or that should be dynamic. Well, now I need to go through and fix ALL areas wehre something like a column or datatable reference was hard coded. If JMP had merely set it up as a variable from its first inseption, I'd change it one spot and be done. Additionally, I may know going into a workflow that things like datatable names or columns may be variable. Making it easy to add variables to the workflow to set as defaults or prompt the user becomes deeply valuable.     Why is this idea important? Workflow builder is extremely cool and lets people automate w/o much background knowledge in scripting, and if nothing changes it works great. JMP already does well when it encounters potential differences, and adding better variable handling helps take all that to the next level. Additionally, variable handling as native to the process will offer additional 'training' to those getting used to scripts when scripts are exported as rather than seeing hard coded vallues everywhere, it's clear you are setting variables and using them throughout. The only caveat/change? may be that workflow builder jsl exports might need to create it's own workspace to live within (the last thing we need is a massive 'local' wrapper to guard against variable collisions).     ... View more

What inspired this wish list request?  The inspiration for this request stems from a limitation encountered when trying to calculate the mode of string (categorical) data while simultaneously grouping it by another variable. Currently, the  Col Mode()  function, which is designed for grouped calculations, exclusively accepts numerical arguments. This means that if a user has a column of string data (e.g., product names, customer segments, error types) and needs to find the most frequent string within distinct groups (e.g., by region, date, or machine ID),  Col Mode()  cannot be used directly.   What is the improvement you would like to see?  The improvement I would like to see is for the  Col Mode()  function to be enhanced to accept string (text) columns as valid arguments for its main calculation. When a string column is provided,  Col Mode()  should perform the same grouping logic it currently uses for numerical data but apply the mode calculation appropriate for strings within each group.     ... View more

☑ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ just nice to have ☐ nobody needs it     #myTop10_2026 What inspired this wish list request? I was very surprised to learn that there is currently no way to fully transfer all my JMP settings when installing a new major version. TS- 00283930 Some preferences can be handled via JSL (e.g. with @jules 's  excellent Preferences Manager), but many important settings are left behind and need to be recreated manually after every upgrade.    What is the improvement you would like to see? I would like JMP to provide complete migration of all user settings between major versions – not just the subset that is currently JSL-accessible. Concretely, the improvements I imagine are: A built-in mechanism that covers all relevant user settings, including for example: Favorites in the Formula Editor (most used functions pinned at the top), Recent Settings in platforms, all other preference/UI settings that are currently stored outside the portable, scriptable preference framework. A safe, supported migration flow with two user-friendly options: At install time: Dialog like: “A previous JMP version was detected. Do you want to copy your settings from JMP XX to this new version?” One click → all compatible settings are transferred. Inside JMP (menu-based): Command like: File → Import preferences from previous version… User can explicitly trigger migration later, again copying all compatible settings from the immediately preceding version. This should be implemented in a way that: does not rely on direct manual write access to configuration files (which is fragile and risky), extends and completes the existing portable preference framework so that tools like Julian’s Preferences Manager can also benefit from broader JSL coverage in the future. Why is this idea important? Losing key preferences on every major upgrade feels like a bug rather than a missing feature. For experienced users who invest time in tailoring JMP to their workflow, it is a real productivity killer: Efficiency: Rebuilding favorites in the Formula Editor or reconstructing platform “recent settings” by hand after each upgrade costs significant time and interrupts productive work. Consistency: Users who do not have the patience to reapply settings end up working with suboptimal, inconsistent environments across versions, which undermines the value of upgrading. Adoption & satisfaction: If upgrades come with the hidden cost of “starting over” in terms of configuration, users are less motivated to move quickly to new versions – even when they bring important improvements. Safety & robustness: A JMP-native migration mechanism is safer than ad-hoc copying of configuration files. It avoids the risk of crashes or undefined behavior while still giving users the comfort of a familiar environment in each new release. In short: JMP already shows, via tools like Julian’s Preferences Manager, that preference portability is possible – but today it is incomplete and constrained by which settings are script-accessible. other wishes from  ... View more

What inspired this wish list request?  Have more than 30scripts in each file - this export option will help exporting each plot into a word or ppt slide avoiding manually copy pasting them over multiple JMP files.   What is the improvement you would like to see?  Have more than 30scripts in each file - this export option will help exporting each plot into a word or ppt slide avoiding manually copy pasting them over multiple JMP files.   Why is this idea important?  Have more than 30scripts in each file - this export option will help exporting each plot into a word or ppt slide avoiding manually copy pasting them over multiple JMP files. This will help save time.   ... View more