JMP Wish List

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

☐ cool new feature ☐ could help many users! ☐ feels like a „bug“ ☑ nice to have ☐ nobody needs it   Surprising, especially for new users of Jmp: A local data filter doesn't exclude items, which are already excluded by a global data filter. Data Filter: exclude excluded rows    For users who work with Jmp for many years, this can be a quite logical thing. But if you think about it objectively, it's completely unnecessary, right? So, why?!    In the example from the link above, a data filter which could look like this actually looks like this (excluded, unnecessary items marked red): A user who selects age = 13, 15,17 will not see any update in the graph; could be that he wonders what's wrong.   There is a functionality to exclude data from a graph - why not use the same functionality to exclude the items from the data filter lists? It's already possible to apply such an exclusion manually, bu "conditional" data filters and an additional column with formula excluded(). But this requires some effort.   My proposal: a checkbox in the context menu of the local data filter: don't show data points which are excluded by the global data filter  Then the user can decide if he wants that excluded rows are listed in the data filter (checkmark = 0) or if they should be removed (1) ...   Hm .. actually I can't think of any application case where a user intentionally decides to get excluded items listed. But definitely, there will be some special cases ... Can anybody give an example?         more wishes submitted by   ... View more

☐  cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   my wish: please add a Recall button to the Multi File Import Dialog.         more wishes submitted by   ... View more

☐ cool new feature ☐ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   At the moment, a data table object is removed from Application Builder as soon as the user closes the corresponding data table. This destroys all links to the data table (plots, column list boxes, data filters ...), leading to a non-functional Application. If the user doesn't notice the problem and saves the Application, the file gets useless:      Workaround for users who already lost an application: Don't use Application Builder. Apply extreme care, when an application is opened in edit mode: First save and close the application, then close the data table if the user detects that "it happened again" before he closes the application, he can recover/keep the structure by adding a new data table before saving :)   My wish:  Please protect the user from this problem. Options: If a user closes a data table and the data table is used in an application, please display a warning message asking the user if he really wants to close the data table - as this will destroy the application. Keep the structure in the application as it is (even with closed data table) if the user wants to continue editing the application, Jmp can ask the user if it's OK to open the data table again.     https://community.jmp.com/t5/Discussions/Collection-of-quot-funny-quot-JSL-newbie-questions/m-p/580077/highlight/true#M78727   ... View more

As a code editor JMP's Script Editor is lacking quite a many features, one of them are some fairly basic shortcuts which make writing scripts much faster (and easier when you get used to them) and the shortcuts should mostly work without using mouse. Below are just few of the suggestions that come quickly to my mind (the shortcuts for all of these should be easy for user to configure): Open search bar for Scripting Index This should open similar search window as Quick Open does Open scripting index for current function, this has already been suggested but closed as delivered, BUT this new shortcut requires usage of mouse. Cut Line Copy Line Move Line up/down Copy line up/down Auto-complete variable names (might be already suggested) Either in similar manner as valid commands works currently (Ctrl+Space) Or offer suggestions and user can fill them by pressing Enter This could be expanded to functions in a similar manner as SAS in which you can control how it works through preferences These kinda already exist but have been split into two different shortcuts instead of toggle. I have no idea though how to use these with my keyboard or how to set them in JMP Menu Editor as I don't know the Built-in command for these and they aren't visible (do I have to build them by using Main Menu("")?) Toggle line comment Toggle block comment More possible shortcuts can be found for example from Visual Studio Codes keyboard shortcut listing ... View more