JMP Wish List

Consider the below code: Names Default To Here( 1 ); New Window( "SetKey Example", mb = MouseBox( tb = Text Box( "Press a key." ) ) ); mb << setkey( Function( {this, key}, show( key ) ) ); mb << setkeyenable( 1 ); mb << setfocus; Pressing a button, such as K, causes the attached function to run twice.  Clearly one can produce a work-around with timing and such, but I think that even the JMP developers would consider such user-based work-arounds to be unfortunate.   What inspired this wish list request?  (your template dropped my response to this question)   What is the improvement you would like to see?  (your template dropped my response to this question)   Why is this idea important?  (your template dropped my response to this question)   ... View more

What inspired this wish list request? Challenges with establishing the ability to pull data from SharePoint lists and/or files stored on sharepoint.  SharePoint is a tool that is used for managing tasks and incoming work.  There are several instances where we would like to be able to pull from these lists to use the data for metrics and dashboards.  Connecting to the lists and having the ability to pull in files (.jmp, .xlxs, .csv) that are stored on the SharePoint is very important to use.   What is the improvement you would like to see?  Something similar to what is available to Google Docs to allow easy access to import SharePoint lists and documents stored on a SharePoin   Why is this idea important?  To ensure metrics are accurate and up to date.   ... View more

What inspired this wish list request? Use of a custom script may be required for standard analysis workflow and these are not included in the action recorder.  Also would be nice to be able to use this to demonstrate and record testing scenarios that was performed on these custom scripts for GxP documentation.   What is the improvement you would like to see?  Add custom script to the action recorder.   Why is this idea important?  We use a lot of custom scripts in routine work, this would streamline the process of automating the analysis.  It would also give us a way to document testing performed on our custom scripts.   ... View more

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it     What inspired this wish list request?  Strange that that function is not available in the formula editor (statistical) or JSL... Maybe next version.     What is the improvement you would like to see?  please synchronize the different platforms: - Tables-Summary - Tabulate - Header Statistics - new column formula right click menu - JSL aggregation function  - and most important:   Summary Statistics in Graph Builder every aggregation function which is available via Header Statistics could/should be available via the other "platforms" as well.   At least:  - add a JSL function Col N Unique. - add a unique entries to the new column formula  menu - and in Graph builder, add  Statistics for Unique entries. - and please (!),Add dense ranking to Ranking Tie and Col Rank functions  missing entries should not be counted (see below) for the JSL function: option to count /not count missing entries   Why is this idea important? In Semiconductor Industry, users often ask: - how many wafers (in this list of devices) - how many batches (in this list of wafers)   other JMP users need the functionality for: - how many countries (list of covid affected people) - how many companies (list of employees) - how many cities (list of people) In JMP it's too complicated to get such answers! Header Statistics is great - the other platforms should be optimized. I guess, no user complained about "too many" options in the Header Statistics? Nevertheless, to save newbies from crowded lists, the additional options could be hidden in a submenu - or behind a Shift-Click. * )available via header statistics nominal: continuous:     more wishes submitted by   ... View more

What inspired this wish list request?  When writing jsl scripts that update large tables it is cumbersome to add a <<begin data update() and <<end data update() on either side of the for each row().   What is the improvement you would like to see?  I would like to see some functionality for <<begin data update() and <<end data update() embedded in the for each row() function.   Why is this idea important?  This will make code more readable and faster if users write all for each row() using the new functionality. May improve GUI speed as table updates will be faster.   I am using JMP 16.2   ... View more

What inspired this wish list request? I am trying to automate (JSL code) the redundant admin tasks that consume too much time. My company uses Sharepoint, Teams, and Outlook and having JSL code "easily" communicate with these programs would make life much easier.     What is the improvement you would like to see? Sharepoint and Teams - be able to pull import data easily. Outlook - be able to send emails and meeting invites via script (maybe without having to hit the "allow" button for each email).     Why is this idea important? save time and have less errors     ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  If users want to access display boxes in reports they always have the problem to get the correct code. Is it ListBoxBox # 3 or #5 nad with an intermediate step to the Panel Box, it then #2 or #1? With Jmp 17 it got a bit better, because a direct code for the display box can be generated by the properties menu. So far so good.    But just try to get a robust code to access the list box in the center of the Update menu - robust even if the user changes the Replace Column setting!   A wonderful trick from Using Display Boxes     : select and deselect the node to check if you selected the right one.   This approach could be optimized by a tiny new feature, implemented in the right click context menu of the JSL editor:   What is the improvement you would like to see?  If a user selects the code of a display box, please add a select/deselect command to the right click context menu. When the user clicks on the command Jmp should send a select command to the display box: myWindow[Panel Box( 3 )][ListBoxBox( 3 )] << select If possible: read the current select state of the display box and toggle it (select -> unselect -> select ...)       Why is this idea important?  The trick from the JSL course is so helpful - but the user always has to write the code, change the code, delete it again. With the new command in the right click context menu, it will be much more fun to find the right code to address a Display Box :)   ... View more

What inspired this wish list request?  When making a new data table I frequently use code dt = new data table() but this throws an error since only new table() works.  Tables are frequently called data tables in documentation and other functions and would be good to support new data table() as an alias for new table().   What is the improvement you would like to see?  Please make a function "New Data Table()" as alias for "New Table()"   Why is this idea important?  Would remove a frequent error when coding in JSL.   I am using JMP 16.2 ... View more

☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2023 we have a workaround -> I don't need it anymore.   What inspired this wish list request?  Short: Tables/Update and Tables/Concatenate destroys my source scripts. STOP THEM !!! Long: Many of the Platforms in the Tables menu provide the option Save Script to Source Table. Is is an elegant way to save the command with all the settings as a Table Script Platform_Name Script. There is even an auto-increment function which prevents Jmp from overwriting previous Table Script with the same name.   But there are two exceptions: Update and Concatenate. As all the other functions, Concatenate saves the command script as a Table Script (name: source) to the output table. Exception: If the option Append to first table is enabled, the main table is the output table - and NO script is saved (perhaps to prevent Jmp from over-writing an existing source Table script?)   For Update the main table is always used as output table. This function saves a table script with the current settings (name: source) to the main table and thereby: overwrites any existing source table script (!). Table / Update - source script collision      What is the improvement you would like to see?  Concatenate and Update should follow the naming scheme of the other Table platforms. i.e. save a script with the current settings to a Table Script with name Concatenate Script or Update Script. An auto-increment feature should be used to prevent Jmp from overwriting existing scripts.     Why is this idea important? The auto-generation of JSL source code is a great feature. But over-writing an existing source code is more ham than good . Fixing the issue will save users from losing their table source script.   The naming convention separates source scripts (name: source;  was used to generate the data table) from Platform Scripts (name: Script; can be used to act on the current data table) ... View more

Add new function which would return values in a list (or matrix if numeric calculation) based on column calculations. We can calculate values with Formula() and << Set Each Value, but we have to place the values in Data Table. It would be nice to be able to just calculate values based on the data table's columns WITHOUT adding new columns which you will have to later remove.   One idea for usage could be something like this (Big Class.jmp) result = dt << Calculate Values(:Height / :Weight); and this would then return me a matrix with :Height/:Weight calculated for each row.   Other example with characters could be result = dt << Calculate Values(:sex ||"_"||Char(:age)); and this would return me a list of each row concatenated with :sex and :age.   ... View more

This would help for example when making numeric encoding for character values. Dense Rank (wikipedia) or calculating orders For example scipy.stats.rankdata offers average, min, max, dense and ordinal ... View more

JMP17 has new function called New Formula Column. It would be nice if it were to return the references to the newly created columns in a list, in similar manner as << New Column does for single column. This would make using this function easier   Names Default To Here(1); dt = Open("$SAMPLE_DATA/Big Class.jmp"); new_col = dt << New Column("Log2[height]", Numeric, Continuous, Formula( Log(:height, 2) )); new_cols = dt << New Formula Column(Operation("Log 2"), Columns(:height, :weight)); Show(new_col, new_cols); ... View more

Currently Action Recorder creates fairly non-robust code by using table names and such. New Workflow Builder is able to offer reference replacements but I would like to go a bit further and have an option in which Action Recorder would use variable names. These should be configurable by user. Also namespace should be used in this case, either some specific one or here (add Names Default To Here(1); to top of script)   Below is fairly simple example created using Big Class and Enhanced Log /*: // Open Data Table: Big Class.jmp // → Data Table("Big Class") Open("/C:/Program Files/SAS/JMPPRO/16/Samples/Data/Big Class.jmp"); // New formula column: Log[weight+1] Data Table("Big Class") << New Formula Column( Operation(Category("Log"), "Log x+1"), Columns(:weight) ); // New formula column: Random Uniform Data Table("Big Class") << New Formula Column( Operation(Category("Random"), "Random Uniform"), Columns(:sex, :height) ); // Report snapshot: Big Class - Graph Builder Data Table("Big Class") << Graph Builder( Size(528, 448), Show Control Panel(0), Variables(X(:sex), Y(:"Log[weight+1]"n)), Elements(Points(X, Y, Legend(4))) ); It would be nice if this could be written in log as (this won't work as it seems like << New Formula Column doesn't return reference to the column like << New Column does, but the idea is still the same) // Open Data Table: Big Class.jmp // → Data Table("Big Class") dt_1 = Open("/C:/Program Files/SAS/JMPPRO/16/Samples/Data/Big Class.jmp"); // New formula column: Log[weight+1] col_1 = dt_1 << New Formula Column( Operation(Category("Log"), "Log x+1"), Columns(:weight) ); // New formula column: Random Uniform col_2 = dt_1 << New Formula Column( Operation(Category("Random"), "Random Uniform"), Columns(:sex, :height) ); // Report snapshot: Big Class - Graph Builder rep_1 = dt_1 << Graph Builder( Size(528, 448), Show Control Panel(0), Variables(X(:sex), Y(col_1)), Elements(Points(X, Y, Legend(4))) ); And in this example dt_, col_ and rep_ are the variable name prefixes user has chosen for these specific object types.   This should make auto-generated scripts a bit more robust ... View more

What inspired this wish list request?  We currently run a very long JSL script. We'd like the ability to save the time each line of code takes once the Time Profiler runs so we can use it to find speed improvements over time. Currently, we have to run every script with the Time Profiler & look for time differences by making a change & then re-running the Time Profiler   What is the improvement you would like to see?  The ability to save the amount of time each line of code takes into a text file would be helpful to compare scripts over time. This way, there wouldn't be a need to re-run scripts when asked about a specific function or statement, the data would already be accessible.   Why is this idea important?  Data is constantly increasing & with it, scripts take longer to run. The ability to identify code blocks that are causing slowdowns are critical to maintain efficiency.    I'm currently using JMP 17.0.0.   ... View more

What inspired this wish list request? I haven't really used JMP's Dashboards because Tab Page Boxes they use take too much space and because of this I always write my own UI using New Window(). I could see myself almost using Dashboards (at least as a starting point) now that JMP17 provides quite clean script if I didn't have to clean the code to remove Tab Page Boxes. This isn't as big of an issue in Dashboard view but more on the created script, though I would also like to be able to have dashboard without the "title boxes"   What is the improvement you would like to see?  Provide an option to not add the Tab Page Boxes. Below is fairly simple example with one graph builder and one distribution (script taken with  from Dashboard above): I have basically three mostly useless Tab Page Boxes there, I already know this is a dashboard, I already know I have a Graph Builder and Distribution , I don't need the Tab Page Boxes to tell me that (I also have Outline Boxes telling me this). I would like to be able to have Dashboard which look more like this:   Why is this idea important?  Allows easier creation of compact UI's. Especially with JMP17 change in which the Dashboard script isn't a huge mess anymore (! ... View more

WHAT'S GOOD ABOUT JMP JSL (JMP Scripting Language) is a great tool to ensure reproducibility of your analysis. While it requires some learning for you to be fluent, fortunately, JMP lets you do some analysis with GUI and get a script to reproduce it by clicking the "Get Script" option. This is essential for both learning JSL and making efficient use of it. JSL offers multiple ways to achieve a single task.   THE PROBLEM "Get Script" of most platforms gives you a kind of JSL that's not very popular, the one with "SendToReport" and "Dispatch". For example, the following is a script suggested in "Scripting Platforms" Chapter of the Scripting Guide:   Open( "$SAMPLE_Data/Big Class.jmp" ); // I added this line   oneObj = Oneway(   Y( :height ),   X( :age ),   Each Pair( 1 ),   Means( 1 ),   Mean Diamonds( 1 ) ); oneObj << Unequal Variances( 1 );   rep = Report( oneObj ); rep["Oneway Anova"] << Close( 1 ); rep["Means Comparisons"] << Close( 1 );   Running this script, you will get a Oneway platform with a nice graph. Now, you select "Get Script" from the red triangle menu of the report and get the below: Oneway(   Y( :height ),   X( :age ),   Each Pair( 1 ),   All Graphs( 0 ),   Means( 1 ),   Unequal Variances( 1 ),   Composition of Densities( 1 ),   Mean Diamonds( 1 ),   Std Dev Lines( 1 ),   SendToReport(     Dispatch( {}, "Oneway Anova", OutlineBox, {Close( 1 )} ),     Dispatch( {}, "Means Comparisons", OutlineBox, {Close( 1 )} )   ) );   This is completely different from the one suggested in the Scripting Guide, and is generally less easy to master.   SUGGESTED IMPROVEMENT I wish JMP allows the user to choose the type of JSL to be produced. For those who regularly use "Save Script" for reproducible analysis, this would be a tremendous time saver. ... View more

Activity Recorder is great tool in JMP to quickly automate simple processes. I feel like it should be able to combine different actions into one, currently depending on how you perform actions it creates longer scripts than necessary (these can also make scripts a bit less robust). Below is an example using Big Class with a quick way to create new formula column in JMP (very simple example): Double click to "free" header to create new column (Often we might even have additional step here, which is just renaming the column) Double click on the new column, rename it and set formula column property My enhanced log without the second step: // New column: Column 6 Data Table("Big Class") << New Column("Column 6", Numeric, "Continuous", Format("Best", 12) ); // Change column info: NewCol Data Table("Big Class"):Column 6 << Set Name("NewCol") << Set Formula(:height * :weight); What I would like the Action Recorder be able to do is to combine these into single step which would look something like this // New column: NewCol Data Table("Big Class") << New Column("NewCol", Numeric, "Continuous", Format("Best", 12), Formula(:height * :weight) ); I can already get this but I have to use different method for column creation. Right Click on free column header and select New Columns and fill the required information. In this case we will get much cleaner script: // New column: NewCol2 Data Table("Big Class") << New Column("NewCol2", Numeric, "Continuous", Format("Best", 12), Formula(:height * :weight) ); Though this option won't let me insert columns between other columns.   There are most likely also other places where it would be helpful if Action Recorder could combine different steps. ... View more

Currently if you want to add column to a function used in Formula Editor you have to either Drag and drop the column to correct place Select the place you want to add the column into and then double click the column to add it Open the formula as JSL script and write the column reference My suggestion is that new option should be added: right click selection for the columns (in best case only valid columns would be showed in the list). Right click menu would make it easier and faster to add new columns to functions, especially when you are writing more complicated ones / want to edit formulas.   JMP does already offer quite a few options in the right-click menu for Formula Editor, but I think column selection would fit there within the first "block". Quick paint example: ... View more

Problem When JMP imports data, e.g., a CSV or an XLSX file, JMP guesses the appropriate Data Type and Modeling Type for each Column. This guess is helpful but is not (cannot be) perfect for every scenario. When a large table, e.g., one with hundreds of Columns, is imported, subtle imperfection of the guessing may lead to a lot of repetitive manual work afterwords. Specifically, JMP treats all Numeric Columns as Continuous.   Suggestion I believe many users will benefit if some simple rule-based branching is added here. A specific example of such rules can be adding an option to treat Columns which contains only integers contains only a small number, e.g, 10 or less, of unique values as Nominal.   I believe this applies to all recent versions, e.g., 14, 15, 16, and 17. ... View more