JMP Wish List

Hi.  I'm interested in a function that could be used to remove repeated characters from a string.   What inspired this wish list request?  If I have a string that contains the same repeated character and sometimes I want to remove all but one instance of that character.  For instance, I have a string like "input1;;;;input2;;;input3", and I want to convert it to "input1;input2;input3".  I assumed I could just use SubstituteInto(str, ";;", ";") and it would recursively remove all repeated ";", but did not.  Instead it just would replace only the first 2 semicolons with a single semicolon, then stop.     str = "input1;;;input2;;;input3"; SubstituteInto(str, ";;", ";"); Show(str);   //returns "input1;;input2;;;input3"   Note that the first set of semicolons was reduced from 3 to only 2, and the second set was not affected at all.  My current workaround is to embed this in a while loop:   curlen = Length(str) + 1; While(Length(str) < curlen, SubstituteInto(str, ";;", ";"); );   //returns "input1;input2;input3"   What is the improvement you would like to see? I'd like to see a modification to the Substitute(), SubstituteInto(), and Munger() functions to include a "<< RECURSE" message that just makes it perform the same operation as the code above: Substitute(x, patternString1, replacementString1, ..., < <<IGNORECASE >, < <<RECURSE >); SubstituteInto(x, patternString1, replacementString1, ..., < <<IGNORECASE >, < <<RECURSE >); Munger(s, startpos, findstringOrNChars, <replacestring, < <<RECURSE > >); Alternatively, rather that change established functions, perhaps a new function could be created called "Trim Multiple()" Trim Multiple(s, patternString); where s is a string and patternString is one or more characters.  The code will search through s for any instances of patternString that are repeated consecutively.  Where it finds one, it replaces it with just one instance of patternString and continues searching s for more instances of patternString. Why is this idea important? This would reduce the complexity of users' codes.  It would also be a way to help to highlight to users that the Substitute()/SubstituteInto()/Munger() functions are -not- inherently recursive, and in doing so this would help prevent bugs.   ... View more

What inspired this wish list request? Getting connected to database from JMP  can take a while, especially with JMP 19, see: JMP19 needs a lot longer for database queries - JMP User Community So it would be a valuable information for an application, which connections are accessible quickly, as well as for user information. What is the improvement you would like to see?  I would need e.g. a function, that gives the "open" or established connections per session (e.g. where authentification is not neccessary anymore), see Re: How to get database connections that have been used in current JMP session - JMP User Community Why is this idea important?  it helps to make applications more effective and user experience better (less idle time)     ... View more

What inspired this wish list request?  Currently, the Filter View in JMP is rigid and not customizable. All filters are displayed vertically, which quickly becomes cluttered and inefficient when working with large datasets. There is no way to rearrange, resize, or group filters in a way that matches the user’s workflow. Additionally, users cannot add custom buttons or actions to streamline repetitive tasks. For example, when analyzing survey data with dozens of categorical variables, the vertical-only layout forces constant scrolling and makes it difficult to focus on the most relevant filters. This slows down exploration and reduces usability   What is the improvement you would like to see?  Allow customization of the Filter View layout (e.g., horizontal arrangement, collapsible sections, drag-and-drop ordering). Enable adding custom buttons or actions directly in the Filter View or Data Filter, so users can trigger scripts, apply presets, or perform common tasks without leaving the interface. Provide options for styling and resizing filters, so the interface adapts to different screen sizes and user preferences. Ideally, the Filter View should behave like the Data Filter but embedded inside the data table, with the added flexibility of customization       Why is this idea important?  Ease of use: A customizable Filter View would reduce clutter and make data exploration more intuitive. Efficiency: Custom buttons would save time by automating repetitive actions directly within the filter interface. Flexibility: Different users have different workflows; customization ensures the tool adapts to them rather than forcing a rigid layout. Value: The Filter View is already a powerful feature since it mirrors the Data Filter inside the table. Making it customizable would unlock its full potential and make JMP more competitive with modern analytics tools. In short: the current UI feels outdated and restrictive, but with customization and the ability to add custom actions, the Filter View could become a must-have feature for everyday JMP users.   We have around 150 licenses who use JMP and JSL for scripting in our organization.       ... View more

What inspired this wish list request? For many users JMP is the standard application for data analysis, and Sharepoint is the standard collaboration platform. That Sharepoint can not be used in a safe and convenient way to share JMP files is a substantial drawback for many companies. See earlier wish of @hogi for more details: Optimize Sharepoint Integration - JMP User Community The planned data connectors the way I understand will not fix this issue.   What is the improvement you would like to see?  I would like to see a builtin capability of JMP to: open a file from Sharepoint (and lock it in readwrite mode if not already locked, if already locked open it in readonly mode) possibility to work with that file like with files from other sources and close+save the file after making changes (and release file on Sharepoint for others to change)  Seemless integration (many users working together in one JMP file) is not possible in overseeable future, but above features are feasible and reasonable in my opinion.   Why is this idea important?  JMP's inability to work with SharePoint disrupts our company's workflows and requires additional ressources and opportunities for errors in dealing with it.     ... 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

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

What inspired this wish list request? With JMP19 on the scene, I noticed an auto update feature for addins where JMP will look for udpates to files from an 'install folder'. The implementation was a bit "clunky" and ends up breaking a bunch of infrastructure we already had built.     What is the improvement you would like to see? Rather than living in the Views > Addins settings, these choices should be codified in the addin.def file all addins need. It will make it easier for those with existing infrastructures to manage as well as easier to implement part of JMPs cool features iteratively.     Why is this idea important? I want to take this feature to the next level. It's a super great idea, but its current implementation can easily cause issues for others. In my current infrastructure, updates are checked for against a master list to know when new versions are released. JMP's feature could deprecate the need for some of this, but it needs more finesse in how it's laid out. Some examples: 1. Addin installed from correct location, all is well... later on user can't access location and needs the update. I pass along the jmpaddin file to them so they can keep on going. They drag it into JMP ... now it's possible the install source is now the downloads folder and they wouldn't get notified of updates because of that change ... hard coding the correct source into the def file would allow this to work regardless. 2. Testing addins. Similar to #1 if you have a folder where your tests are located, installing a test file would change your install location to the test location and they wouldnt get notified when a new prod release happens. And depending on how files are named they may or may not be notified of new test versions ... because test versions are often 'handed' off, they include teh version in the filename... so an exact filename match isn't possible for the update checks. In both of these examples, there are aspects of what JMP has done that could be useful, but the deployment team needs more control in how their addins shall be marked for update. There are probably more example, but I think this is enough to get the ball rolling for the update 'stuff' to be part of the addin.def file with one or more variables there.   Thanks!     ... View more

What inspired this wish list request?  A comment/conversation at the The JMP Inspire event in Intel Ireland. A wish list item that was mentioned that I realized I wanted too.     What is the improvement you would like to see?  Add option to Save Script To New Script Window. The option to Save Script To Script Window exists today. This appends to existing script window if already open. Sometimes it is preferable to start a new script window. (Achieved today by copying script to clipboard, launch new script window and then pasting from clipboard).    Why is this idea important?  Will save time and clicks.      ... View more

☐ cool new feature ☐ could help many users! ☑ removes something that can act as a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  see: Disable "Update Table" script?  After an Excel import, JMP automatically adds a "Update Table" script. This script can be used to update the JMP data with new data from the input data.   Unfortunately, with the update, many properties of the JMP data are lost.   What is the improvement you would like to see?  a) Add an option in the preferences which disables the generation of the update script b) provide an "Update Script" which Updates the data table: universal "update" button for imported data. Join, Concat and Update  - add new data - keep current formatting and properties   Why is this idea important?  users can delete all their formatting, table properties, column properties ... buy an innocent click on      Update Table     ... View more

Would it be possible to add somewhere in settings a way to set the default Item Wrap and Max Items values of Graph Builder to a different number? I often run data with a lot of categories where the Max items is way too short. Not to mention that on a regular screen the Item Wrap almost always ends up wasting a lot of space, instead of doing one long column and allowing the graph to expand. Ultimately a "smart" setting that adapts the layout to the graph and/or window size would probably be ideal, but at least a way to set the default would be a great help.    Thanks! ... View more

What inspired this wish list request? We currently use Statistica to send out emails when there is an out of control data point and we are able to embed the image of the control chart into the body of the email.  I also have daily reports I make in JMP that I save out a PDF and then have to manually grab each morning and email out to user groups.  If I am out unexpectedly this causes issues for user groups that rely on my reports.    What is the improvement you would like to see?  I would like to see the ability to have JMP Live allow embedding of Images and attaching of files.  This would be a feature to use for control chart alarming but also as a stand alone feature to send out a file to a user group from any analysis.   Why is this idea important?  Many users either only have access to their email (such as being on their phone way from a computer) or need to be able to print an output from JMP to post in their manufacturing areas.  By allowing automatic file generation AND Distibution this will greatly enhance the ability of Engineers to automate routine tasks as well as expand the use of JMP for enterprise systems and eliminate the need to use something like PowerBI for Manufactuing reports and SPC. ... View more

What inspired this wish list request? When a dashboard containing reports with LDFs (Local Data Filters) is publised to JMP Live, the auto update feature is turned on automatically. This means that every click elisits a wait for update. Depending on the type of graph, always hving to wait or remember to turn off auto updates is annoying, especially since there is no preference to toggle.     What is the improvement you would like to see? The ability to specify the default Auto Update state (on/off) when publishing dashboards/reports that contain LDFs     Why is this idea important? For something where the graphics may be 'overly complex' to start because different users will want to look at something different, and there are several layers to the LDF (say 3 conditional categories), always waiting for auto update (or forgetting it's turned on - for each report) is a pain. But there is no way for that default to be toggled. No native feature in JMP turns auto update off/on, and there's no control when the dashboard/reports are published to JMP Live.   For my example where I noticed this, the dashboard had 4 reports each backed by a different table and a singular LDF of 2+ categories. Auto update being on by default made the experience more painful as I usually wanted to do more than one thing at a time but each click prompted a wait for the update.     ... View more

Inspiration Our individual user account credentials periodically expire, and we require authentication to access data.  When setting up a report to refresh in JMP Live we wither need to user our own credentials and update them every time a password changes, or use a 'service account' that is created specifically to get this data.  It is not feasible to create a ton of these service accounts, so instead we end up sharing a single account with multiple users. In order for them to use it in JMP Live they need to enter the username and password in their JMP Live page.  This account often has more access than that person needs (it can inherently connect to some things from outside of JMP Live), and having access to the username/password makes it possible to use the account for more than what is needed.    The idea Allow an admin to set up a shared set of credentials and then allow specific users, or groups of users, to access that account without being able to see the username or password. Ideally there would be some check in the script that they cannot print the credentials to the log or to the resulting table, but that could be a later step. This would mirror existing functionality in the enterprise gateway for PowerBI.   Why is this idea important?  Data security: In order for this to become a true enterprise tool, it is going to need to pass corporations increasingly stringent cyber security policies.    ... View more

☑ cool new feature ☑ could help many users!    ("nobody" is using expression handling? - maybe ... why?) ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2025   What inspired this wish list request?    In JSL, Expr() is used for 2 purposes: -  "it is here()" inside of Eval Expr() - I protect you()  - to protect the content from being evaluated Unfortunately, Eval Expr() is  happy with the first Expr() and evaluates it. This restricts the flexibility with which users can write nested expressions - see: Returning an expression from a function differs when namespace is used. TS-00235515 TS-00235798     What is the improvement you would like to see?  Add 2 new functions to JMP for the 2 meanings of Expr(): -  "it is here()   *) " inside of Eval Expr() - I protect you() *)  - to protect the content from being evaluated   *) please use the comments to suggest optimized function names?  - as short as possible - as "telling" as possible    [Name Expr() is the ideal name for Name Expr() - for German speakers ...]   Together with the [legacy] Expr(), they should allow the user to write code much easier in JSL.   e.g.  Eval Expr(protect( ....     Expr(expression to evaluate) ...) ...)   in the sense of  Eval Expr(protect( ....     it is here(expression to evaluate) ...) ...)   Why is this idea important?  the dual-use of Expr() it is harmful and makes code fragile and complicated. Using separate names for the 2 meanings will fix the issue.   other wishes from  ... View more

What inspired this wish list request?    Having to scroll through long code to find a specific line of code that generated an error when reformatting the code or when running the code.   What is the improvement you would like to see?    JSL Script Editor added functionality: When writing JSL code, it would be great to have a functionality where you can right click within the editor window and have the option to "go to line" and enter a line number. This would be helpful when debugging, or when "reformatting" the script and an error is thrown that says you're missing a ";" or ",", or something. This is particularly helpful when working with code that is many hundreds to thousands of lines long -- it beats scrolling and scrolling through code. I appreciate the the right-click > Advanced option for collapsing or expanding Expressions and Functions.   Why is this idea important?    Saves time and improves the functionality of the JSL Editor.   ... View more

What inspired this wish list request? A change was noticed in upgrade from JMP 17 to JMP 18 where all table column names are automatically alphabetized rather than following programmed order.     What is the improvement you would like to see? Return to previous setting where the table column order is how the table was built.     Why is this idea important? Increased burden on large tables to reorder.      ... View more

☐cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  How does one perform Bitwise operations in JMP formulas?  How do I perform bitwise xor operations between columns with 44-bit binary data?    What is the improvement you would like to see?  Native function for bit operations like XOR, shift bits, split bits, get bit, set bit.   Why is this idea important?  could help users who want to do bit operations in Jmp.   more wishes submitted by       ... 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 JSL there are functions like  is control key() to get the current status of modifier keys,   unfortunately,  This function does not return the current state of the control key but rather the state of the control key at the start of another event like mouse click or key press.  Checking for modifier keys (ctrl, alt, shift) in script without mouse trapping      What is the improvement you would like to see?  As  JMP does have an internal function to get the modified key state at any time but this is not exposed via JSL. Checking for modifier keys (ctrl, alt, shift) in script without mouse trapping  ... could you please provide a JSL function to expose the current status of a modifier key :)     Why is this idea important?  This will allow JSL programmers to generate Toolbars and commands in the menu on a completely new level: depending on the status of a modifier key, different actions could be triggered (!!!)   similar add-on functionality could also boost standard platforms: - A user could specify a DEFAULT action in the preferences. If a user clicks on Subset, Summary, Tabulate, Graph Builder - holding SHIFT - the DEFAULT action is executed ... without any need to manually enter the settings. - with a control key, the action could be triggered with the RECALL settings.   other wishes from  ... View more

What inspired this wish list request?    When adding a column switcher to the platform, the list box for selecting columns is often too tall and/or too wide/too narrow.  If the list boxes are resized and then the script is saved for the report, the sizing of the list boxes is not saved.   What is the improvement you would like to see?    Save the sizing of the column switcher list boxes when the script is saved.     Why is this idea important?    The current way to have sized column switchers is to either access the report layer and send a set size message to the list box, or to add the column switchers separately with JSL and use the set size and or/set N Lines messages to that added column switcher.         ... View more