JMP Wish List

it should be possible (like minitab) to set the preferences for a graph with footnotes.   Projekt Name, (Worksheet), Date, Time, Open Text   as footnote on every graph as a requirement from quality standard. So you can find from which file, which sheet, date and the owner who crated the graph.   (that's also why subset should be handled in worksheets within the project and not as new table, outside) All browsers and programs changed from new windows to tabulated screen, within one programm).     ... View more

Many times we run distribution or some another platform and after some changes in the data, we run it again. I suggest JMP will have a command (with key combination shortcut) which opens the last dialog in use, instead of going to menus again and again. Thank you.   ===== From Main Menu - Edit Last Command/Action:   @Simone1 said:   The proposal of this "simple" idea comes from my and some JMP users in the day-by-day activities. In JMP already exist the function "RECALL": but... to use the RECALL function you need to open the dialog box for the specific analysis/graph/...   For the users point of view, could be very helpful to have one BUTTON in the main menu: when you push this button, JMP recall the last your action (and it open the relative sub-menu with the last your input). ... View more

I think it would be awesome if texteditbox() had the ability to have a list of values that it would search from and give a listbox (without messing up layouts) below where you could select possible options. I'm thinking like google or whatever.    something like this Names default to here(1); new window("Test", teb = texteditbox("") ); teb << Set AutoCompleter List({"face", "John", "Denver", "head", "heat"}); // I imagine it would have other flags like teb << Set AutoCompleter Match("All"|"Start"); Where if the match were all it would look like And if it were start it would look like     ... 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! ☑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 something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   Short: Graph builder needs this function:       Long: What inspired this wish list request?  Every Jmp user knows this issue: when you invested 15 minutes to optimize your Graph Builder plot, added some subplots, added some categories and then the legend looks like this - and you need another 15 minutes to figure out which entry in the legend corresponds to which subplot.   When computers started to have several video outputs, computer users had a similar issue: which monitor setting belongs to which monitor ?!?!?   And the programmers had a great invention: an Identify button. The user just has to click the button and numbers will appear: 1) in the overview 2) on each monitor   What is the improvement you would like to see?  1) I want the same functionality for Graph builder. An Identify Button . When a user clicks the button, numbers should appear in the Frameboxes and in the legend: [extreme case to illustrate the unbelievalble help of the suggested function]   ") please also add a button to "reset" the sequence of entries in the legend to a default setting: all entries from the first subplot, then all entries from the second subplot ....   Why is this idea important?  Nowadays it's very difficult to use different color coding in different subplots - as soon as a new subplot is added, all the color settings are scrambled. The unpredictable sequence of entries in the legend makes it almost impossible to efficiently adjust the settings.         more wishes from  ... 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

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

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

☐ 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

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2023   What inspired this wish list request?    Some days ago, I posted here a wish Tables/Update: add aggregation option . The idea: aggregate the data of the update table before it's merged into the main table. This could make Tables/Update much faster (!) AND more powerful.   Hm. Actually a user could implement the feature right away if he applies 2 steps: 1) aggregate via Tables/Summary 2) merge via Tables/Update.   But that's not true - because some aggregation options were proposed which are not available yet in Tables/Summary - those for non-numeric values like first/last entry,  mode ...   So, if there is something missing in Jmp ... let's write a wish (especially as @jthi already proposed to do so: https://community.jmp.com/t5/Discussions/Summarize-Function/m-p/658685/highlight/true#M84794 )   Actuall, in 2019, @ewittry1  posted a first version of this wish - to add an aggregation option for character columns in Tables/Summary (via concat): Summerize/Summary aggregation function for character data. Concat Charcter Vector into a Scalar (by)  Amazingly useful!   Unfortunately, the wish was archived at that time. So, here is a new wish:   What is the improvement you would like to see?  Please add aggregation functions for Character columns  .... to Tables/Summary AND Analyze/Tabulate.   Possible aggregation options are: mode (most common entry) entry of first matching row entry of last matching row concatenate the entries of all matching rows (with space, comma, underscore) option: drop multiples are all values the same? number of distinct values concatenate distinct  *)   Why is this idea important?  With the current version of Jmp, users can use Summary and Tabulate just for numeric values.   With a future version of Jmp users will be able to use Summary and Tabulate for ANY table, including character columns. They just have to choose the character aggregation which fits their needs.   *) I guess there are many more aggregation options for text. What are the other ones?         more wishes submitted by   ... View more

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2022     For Local Data filters, the Select option is missing: https://community.jmp.com/t5/Discussions/Collection-of-quot-funny-quot-JSL-newbie-questions/m-p/579590/highlight/true#M78685   Is the absence of Select mode a fundamental necessity for Jmp to work - or is it just like @ian_jmp guesses: https://community.jmp.com/t5/Discussions/Collection-of-quot-funny-quot-JSL-newbie-questions/m-p/580295/highlight/true#M78738 ~ It's removed because otherwise the user could be confused by the too many possibilities/too much functionality.   I understand that not every user needs a Select option in a local data filter.   But on the other hand - with the select option enabled, you could generate a completely new generation of Dashboards. Even after generation of the Dashboard, the user can add variables to the Data filter - and use them to highlight points in the plots! Thereby, the user of the dashborad is no longer restricted by the creativity of the coder of the dashboard.   The Enhanced Sankey Plot Add-In is a great example of how versatile a Dashbord can be with a select - enabled Data Filter: https://community.jmp.com/t5/JMP-Add-Ins/Enhanced-Sankey-Plot-ESP/ta-p/549745 Here, @jthi uses a generic Data Filter as a universal highlight tool. Wether you want to analyze mushrooms, chips or populations, you will always be able to select the values which you want to use to highlight data points. The only disadvantage here: @jthi  had to use a global data filter to provide the functionality - i.e. with all the disadvantages of a global data filter!   The additional benefit of a Select-enabled Local Data filter: If you just have a GraphBuilder report open, you can enable/disable "Dashboard" mode with a single click on the Local Data Filter Icon on the Report Toolbar. Cool, right? So here is my Wish: Please >don't< disable select mode for Local Data Filters.                 more wishes submitted by   ... View more

Usually I notice in Graph Builder or Distribution that certain Column Properties need to be set or adjusted: Value Ordering, Units, Limits, Value Colors, ... It would save time and make working with JMP more dynamic if those Column Properties were accessible with a right-click on the respective variable within Graph Builder, may it be on the x-Axis, y-Axis or in the Columns box on the left. Having to go through the data table, into Column Properties and then back into Graph Builder interrupts the analysis procedure more than is necessary.   The same goes for Recode. ... View more

Analyze > Screening > Explore Outliers, would like an option to output the results as an indicator column ((0|1), where 1 indicates outlier.   Currently, the result options are: Select Rows, Color Cells, Exclude Rows, Color Rows, Add to Missing Value Codes, Change to Missing. Of course, it is pretty easy to just duplicate the data column, Change to Missing, and then by script or formula turn that into an indicator column. But it would be nice to have Make Indicator Column as a native option. ... 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

☑ 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

☐ cool new feature ☑ could help many users! ☑ feels like a „bug“ ☐ nice to have ☐ nobody needs it   Short: Remove this "bug": ... and this one:             Long: What inspired this wish list request?  If reports are open, Jmp is not able to sort a data table: https://community.jmp.com/t5/Discussions/How-to-update-table-after-sorting/m-p/659014/highlight/true#M84836    Same issue for data tables with linked subsets: sorting and concatenating data to the data table doesn't work. Similar issue if a user wants to add rows to a data table .   linked subset: sort → no add rows → no concatenate → no   open report: sort → no add rows → yes concatenate → yes   What is the improvement you would like to see?  Please remove the restrictions.   e.g. "cut the link", like it's done for linked summary tables: sort → no [why does SORT not "cut the link"?!?] add rows → yes² concatenate → yes²   ² JMP automatically cuts the link:     Why is this idea important?  It's very likely that a user opened a linked subset, a linked summary table or a report before he tries to sort a table or add new rows. Therefore, JMP users face this issue very often.       more wishes by     ... View more

DUPLICATE OF Allow secondary or alternate column names  ☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it #myTop10_2024   What inspired this wish list request?  Often incoming data is quite cryptic and some data curation is needed. Jmp already provides nice solutions, which help the user to curate the data "on the fly", like recode.   Many of the curation steps are "persistent" - such that no further curation is needed when the data table gets updated with the latest data: - formula columns - column property: Value Label - ...   A special issue are column names: Ho to handle cryptic Column names?  Here there is a clear trade-off between human-readability and compatibility to incoming data.   - The user might rename a column -  but then the data table cannot be updated anymore. - the user might add an additional column with the correct name and link it to the original column by a column formula - but this approach is just useful for a few column names. - possibility to give columns different names in different languages - save the alternative name as a new column parameter + Script to toggle between original and alternative column names.   https://community.jmp.com/t5/Discussions/Ho-to-handle-cryptic-Column-names/m-p/722751/highlight/true#M90501    I guess everyone has found their own workaround to deal with the problem. Surprisingly, there is no "official" solution, like column alias   What is the improvement you would like to see?  Please add a new column property: Column alias If a column alias is defined, - the alias column name replaces the column name in the table header, all lists, reports, plots and views. - the alias column name can be used alternatively in filters (so the user can search with the original and the alternative name) - it can be used in Table operations like update and concatenate - as an alternative to the original column name     Why is this idea important?  Significant simplification of data curation :) 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?  Some functions in Jmp take a very long time to get finished. There is a request toSpeed up Tables/Update , because it can take hours to be executed. "Get rows where" is taking way to long  Another issue: Life Distribution. Depending on the size of the data table, the user has to wait for hours: https://community.jmp.com/t5/Discussions/how-to-make-cumulative-probability-plots-in-JMP/m-p/717879/highlight/true#M89957 another application case: Database queries. They can be executed in the background. But then the query cannot be included in a script. The next part of the script has to wait for the data to arrive. Would be great if there was an option to interrupt the query if it takes too long.   For all these cases, it could help to cancel the activity after a specified Timeout interval:   What is the improvement you would like to see?  Option: For Try(), please add a possibility to specify a timeout interval. If the execution of the code takes longer, the script is stopped and the table is reverted to the initial state.Timeout of the try function   Please add a timeout parameter in the preferences. if the user specifies a timeout of 10 minutes, If starting a platform or executing an action takes longer than 10 minutes, the execution is stopped. For actions which alter the data table, the table is restored to the point before starting executing the action. This should be possible because most actions in Jmp have an undo function. I guess a recovery point is stored before starting the action?   Why is this idea important?  There is a Wish from 2020 with 79 Kudos:Kill process without killing JMP ! So, it seems that there is an extreme demand here, but it also seems to be extremely complicated to fulfill the users' wish.   The Timeout concept could be an easy solution. Every user will accept to wait 10 minutes (and get a coffee - or two) instead of losing the results of many hours because an action in Jmp takes orders of magnitude longer than the user expected. more wishes by ... View more