JMP Wish List

As a JMP Partner in Brazil, I teach people how to use JMP to solve problems using data, and I’ve received some feedback on the language options available within JMP. While multiple languages are supported, Portuguese is not yet one of them. Including Portuguese would be a significant step toward expanding the JMP community in Latin America. Brazil is a huge market with tremendous potential! Although there are thousands of JMP users here, not all are fluent in English or Spanish. Our competitors’ software includes Portuguese support, which often makes it the preferred choice for some users. Adding a Portuguese option would greatly benefit the JMP community and increase adoption across Brazil. Thanks! ... View more

What inspired this wish list request?  The search bar in the Data Filter clears any previous selections.  This makes multiple selections from long lists of many levels really tedious; you have to scroll through the entire list to make your selections.     What is the improvement you would like to see? The search bar in the Data Filter should not clear your previous selections.   Why is this idea important? This feature would enable easy & fast multiple selections from long lists.  I'd like to use it to select ingredients from a standardized list of all of our raw materials that would feed a DOE factors table.  This way, scientists are all using the same names/identifiers for ingredients in their DOEs.  Without this feature, I'd have to build a bespoke tool & JSL scripts to do this.         ... View more

What inspired this wish list request?  Creating complicated formulas which would be extremely simple by being able to calculate them in subset.     What is the improvement you would like to see?  Let us add formulas to linked subsets which would then provide the values back to the original table. If the row is not in linked subset all the values should be empty and otherwise they should be calculated based on the linked subset. We can do this basically without formulas, if we add index column and update values back to the main table but formulas makes it more visible what is being done.   Below is one example: We wish to calculate cumulative sum of the last height of each age. We can calculate it with a formula such as (which is unintended but one of the best formula features JMP has Make using formula expressions in Set Each Value and using expressions as first argument in Col statistical formulas supported behaviour ) If(Row() == Col Max(Row(), :age), Col Cumulative Sum(If(Row() == Col Max(Row(), :age), :height, .)) ) Now if we were able to use this "linked subset reverse formula" we could take a subset of those values (many ways to do this). Just by having the formula in original table Col Cumulative Sum(:height) and looking at the preview, when we have link to original data table enabled, we can see that it calculates correctly (Column 7). I would somehow like to be able to add this "subset" formula to my original table.   When I click OK, it reverts back to original values and calculates "incorrectly". This is bugged either in preview or in the subset. I would prefer to have it like this in subset BUT I think it would require some additional option added as it isn't same value anymore as you would find in the original table.   Currently I can create NON-LINKED subset with copy formula and then use update to add that back to my original table (first change column name) but this way there is no more indication how those values were calculated (unless I script the whole thing / use workflow for a bit clunky documentation)   Why is this idea important?  Would make linked subset more useful and performing some calculations easier while still having them documented as formulas. ... View more

What inspired this wish list request? I was working on a dataset with thousands of rows and hundreds of columns, and I saved dozens & dozens of scripts to document my exploratory data analysis and model development process.  I organized the scripts in the script window by grouping them together.  Whenever I received new columns of data, I joined the new data to the large dataset, and the resulting table inherited the scripts from the primary table but the script groupings disappeared. I had to redo the script groupings each time (or copy/paste the new columns into the primary table which is error prone).      What is the improvement you would like to see? Table operations create new tables that inherit the primary table's scripts and the script groups.     Why is this idea important? Maintain script organization as datasets and analyses grow in complexity.  Not all data comes back at the same time, and new questions can be raised over time.     ... View more

What inspired this wish list request?  This post No output result for summation of multiple columns    What is the improvement you would like to see?  Change quick formula Sum to use Sum() function instead of + as Sum() is able handle missing values. Optionally add other Sum() option which would use Sum (or rather add Add() which would be using Add() or + and Sum should utilize Sum()). https://www.jmp.com/support/help/en/18.0/#page/jmp/statistical-functions-2.shtml?os=win&source=application#ww2755226   Why is this idea important?  Gives users option have quickly calculated sum column without always running into issues with missing values. ... View more

What inspired this wish list request?  Building JMP formulas which require a bit more than just referencing always the same column names     What is the improvement you would like to see?  Provide as a way to easily access the data table in which the formula column is in. Currently you either have to do scripting and evaluate expressions or use Current Data Table() which Formula Editor doesn't like This would give as an option then to get all the column names for example while using As Constant to have a bit more dynamic formula.   Why is this idea important?  Makes it easier to build more complicated formulas without seeing warnings in formula editor. ... 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?  When a user renames a column, Table Scripts get automatically updated. When a user deletes a column which is used in a table script, JMP warns the user if the column is used in column formulas. But a table script will die without notice.   a) it takes a long time for the user to find out why the table script is dead. b) it takes some effort to create the column again (worst case: not possible to create the column again)   What is the improvement you would like to see?  Before deleting a column, please check if the column is used in a table script - and show a warning.   Names Default To Here( 1 ); Current Data Table() << copy table script( "no data" ); tableScript = Eval( Eval Expr( Parse( Expr( Get Clipboard() ) ) ) ); col_names = Current Data Table() << Get Selected Columns(); tableScriptList = Substitute( Name Expr( tableScript ), Expr( New Table() ), Expr( List() ) ); tableScriptList = Filter Each( {part}, tableScriptList, Head( Part ) == Expr( New Script() ) ); found = 0; For Each( {col}, col_names, For Each( {myScript}, tableScriptList, If( Not( Is Empty( Eval( Eval Expr( Extract Expr( myScript, Expr( Name Expr( col ) ) ) ) ) ) ), Caption( {100, 200}, "column \!"" || (col << get name()) || "\!" found in script: \!n" || Arg( myScript, 1 ) ); found = 1; print("found!!!"); Wait( 1 ); ) ) ); If( Not( found ), Caption( {100, 200}, "no column found.\!N ->cols can be deleted" ); Wait( 1 ); ); Caption( remove )   Why is this idea important?  Just imagine how many JMP users killed a table script by "accidentally" deleting a column. switching to "safe mode" will safe many users from the same issue.     other wishes from      ... View more

What inspired this wish list request?  Creating anonymized datasets and still having non-anonymized data.   What is the improvement you would like to see?  When user anonymizes data table this error message should give option to remove the scripts and variables, not just inform user about them (or I'm not really sure why they are even left there, the dataset is anonymized, they won't work anyway).   Why is this idea important?  Makes it less likely to share non-wanted data "hidden" in table scripts/variables. ... View more

What inspired this wish list request?  Always writing more or less complicated scripts to "clean" my data tables (remove table scripts, table variables, column properties, ...)   What is the improvement you would like to see?  Provide easy platform to cleanup data table. This should give option to remove table scripts, table variables, column properties, row states and all different modifications. In best case user could decide which to remove. Some of these could be implemented to Subset but I feel like this should also be separate platform.   Why is this idea important?  Makes it easier to create new data tables from existing ones without they carrying over non-relevant information. ... View more

What inspired this wish list request?  Using JMP's Update platform and getting error messages.     What is the improvement you would like to see?  If user has defined columns to be added and chose NOT to replace any of those added columns, add them as new columns with index.   Error:   Names Default To Here(1); dt1 = Open("$SAMPLE_DATA/Big Class.jmp", Invisible); dt2 = Open("$SAMPLE_DATA/Big Class Families.jmp", Invisible); dt1 << Update( With(dt2), Match Columns(:name = :name), Add Columns from Update Table(:age), Replace Columns in Main Table(None) ); Close(dt1, no save); Close(dt2, no save); but I would like to end up with two age columns: original age and newly created age 2 from the dt2.       Why is this idea important?  Makes using Update more flexible without having to rely on renaming columns     ... 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?  For linked data tables (either summary tables or linked subsets),  a click on  will take me to the original data table. This is very convenient. Great that JMP is willing to share this knowledge.   Unfortunately, there is no corresponding functionality available via JSL - to get from a linked summary table or subset table to the main table.   What is the improvement you would like to see?  For reports, one can use the message << get data table()t o get a reference for the data table. For linked summary tables and subset tables, please provide a corresponding message to get a reference of the original data table.   Why is this idea important?    Just imagine how often you generate a report from a summary table - and then face the difficulty how to save the script. Actually, it's just a combination of  a) the source script for the summary table b) the source script of the report ... but it requires ~ 20 mouse clicks to save the combined script to the main table. If there is a way to get the main table - all this could be triggered by a single click on a toolbar. cool, right?   other wishes from  ... View more

☐ cool new feature ☑ could help many users! ☐ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2024  What inspired this wish list request?  JMP provides many useful platforms and great functionality for exploratory data analysis.   But even after 18 versions of JMP - there is still some low-hanging fruit to be picked - such as is in spec(value)        What is the improvement you would like to see?  For a column with Spec limits, please provide   a JSL function is in spec(:value) which compares the value of the current row with the spec limits of the column and returns 1 if the value is in spec, missing, if the value is missing and 0 if the value is out of spec  a functions is out of spec(:value) which compares the value of the current row with the spec limits of the column and returns 0 if the value is in spec missing, if the value is missing -1 if :value[] < LSL +1 if :value[] >USL   Both functions should be available via the right click "new formula column" menu. Then users can easily generate new transform column on the fly in every platform - to group and add color to specific data points.   Why is this idea important?  Is the value in spec is a question that is often asked. Right? -> JMP users will love the new easy to use functions.     other wishes from  ... View more

☐ cool new feature ☐ could help many users! - e.g. in Semiconductor Industry ☐ removes something that feels like a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  Custom Binning is a very cool platform. It's super useful. Thanks @Jeff_Perkinson ! I have to admit - from all the binning schemes, 50% of the time I use Equal Width - and 49% of the time, I define the values manually.   Among the 49 percent, most of the time I want to process a column with spec limits and mark rows which are out of spec.   What is the improvement you would like to see?  If a column has a  property Spec Limit, in the Custom Binning Platform please add options for the two cases: 1) "in spec" and "out of spec". 2) < LSL in spec > USL   Why is this idea important?  The new feature will greatly facilitate the work of users in many industries, e.g. # semiconductor industry   other wishes from    ... View more

このウィッシュリストリクエストのきっかけは何ですか?   What I want to see improved is an issue with imported data when updating from JMP14 to JMP18 (some data becomes null). Specifically, place test data in c\temp, run scripts Source14a and Source14b in JMP14 and JMP18, and compare. Unlike JMP14, in JMP18, when importing data that contains a mixture of YYYY/MM/DD type and YYYY/MM/DD H/MM/SS type in one column, some of the data will be converted to null data.   改善してほしいことは何ですか?   Revert the data import method to the same as JMP14, or add an option to revert to the same as JMP14.   Data that contains a mixture of YYYY/MM/DD type and YYYY/MM/DD H/MM/SS type often occurs in manufacturing sites. If this data becomes null, analysis cannot be performed, so it is important to be able to read it without generating nulls like in JMP14.     この考え方がなぜ重要なのでしょうか?   Customer support also suggested using the Source14aREV script, but it is difficult to change to the proposed script for two reasons. 1) There are already hundreds of scripts running, and it is difficult to change all of them without making mistakes. 2) Even when creating a new script, Source14a format scripts are easily created when opening a file in JMP14. It is very time-consuming for users to convert all date and time data columns in the read data to Source14aREV format (for example, one file contains more than 1,000 rows of date and time data columns).   Therefore, it is very important for the manufacturing industry to improve data reading as a function of JMP, rather than modifying the script.   Apart from this defect, JMP18 is a stable and excellent product. Please eliminate the inconvenience of reading data. If you do so, fewer users will require older JMP versions when renewing their licenses.   ... View more

  ☑ cool new feature ☑ could help many users! ☑ users can remove bugs on their on ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  Via  a user can edit the main menu and [on windows systems] the toolbars.   Other menus cannot be edited. Unfortunately, some of the implemented functions have bugs - and some functions are missing.   What is the improvement you would like to see?  Please add the possibility to remove items from any right click /  red triangle / ...  menu and the possibility to add user defined items. This will allow us to fix tiny issues which won't make it into a future version of JMP - or just in many years. e.g. - Allow us to perform more actions when right clicking on column name on columns panel  - Paste Column has a bug and should be replaced with a version without bug: JMP jumps   Is it possible to customize the Add Formula Column menu to include customize functions?    yes and no: -  a user can not add  user-Defined mini GUIs , e.g. to add Modulo to the portfolio. - Existing functions cannot be added to the menu by name.   (TS-00152405)     Why is this idea important?  Less pressure on JMP developers to bugfix and fine-tune the GUI. Users don't have to wait for version N+2. -> Users will be able to bugfix and tweak the GUI on their own.   other wishes from  ... View more

☑ 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  ... 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?  Data tables with images in JMP are extremely useful! But the usability for other programs is quite restricted.   1) since JMP18, one can directly access data tables from Python. But columns with images are not supported.  https://community.jmp.com/t5/Mastering-JMP/Developer-Tutorial-New-Python-Integration-and-Scripting/tac-p/747694/highlight/true#M503    2) like JMP, Excel supports data tables with images in cells. But when I export a JMP data table with images, I just see the JSL code in the cells. data table with images -> Excel    What is the improvement you would like to see?  1) Please provide direct Python access to column with images. The images should be accessible as images.   2) When exporting data tables with images, please provide an option to export the images as images - and not as JSL code.     Why is this idea important?  1) will be extremely helpful for Python machine learning  algorithms with image analysis   2) will be quite useful to share graphical results with nonJMP colleagues [when further editing of the data table is required]       other wishes from  ... View more

What inspired this wish list request?  Making small mistakes when launching JMP Platforms and I already have implemented this to my platforms.   What is the improvement you would like to see?  I would like to see "Keep dialog open" checkbox in all of the JMP platforms which have a launcher and close it when you press "OK". Other option would be to provide some sort of "Preview" for the platforms but this would be much more complicated to implement to not slow down platforms too much.     Why is this idea important?  Making very small mistake in JMP launcher forces you to find the launcher from menus again and pressing Recall or you can use View/Recall Last Platform (hidden inside menus and has very bad shortcut by default as it forces you to remove your hand from mouse). ... View more

What inspired this wish list request?  Removing all columns from quick columns can be unintuitive. Let's say you pick two columns to group by but then you wish to remove those. You will have to select EXACTLY those two columns to clear group by -> if you select any more those will be added to group by, if you select all columns old ones will be removed and new ones added. So you end up in this cycle where you are continuously right clicking on separate columns and checking which columns are still in group by.   What is the improvement you would like to see?  I would like to see few possible changes.   1. Add new option "Clear Group By". This would remove all columns from the group by   2. Figure out how to make adding/removing columns more intuitive (add new buttons Add to Group, Remove From Group? instead of just having a toggle). Example follows:   I have Semiconductor Capability table open and I wish to create grouping column. First I think I need to have lot_id and wafer as my group columns, I select then and make them into the group. Then I remember that I have to include SITE to my group. I still have my lot_id and wafer selected so I just add SITE to selection and click group by What I will end up with is just SITE in the group And it can get even messier when you try to add more columns and finally try to clear them...   Why is this idea important?  JMP is interactive tool and it should be easy to use as possible. Currently it feels like it is easier to just write formulas using JSL than interactive columns, especially if you happen to mess up with group by column selections even once. ... View more