cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
JMP Wish List

We want to hear your ideas for improving JMP software.

  1. Search: Please search for an existing idea first before submitting a new idea.
  2. Submit: Post your new idea using the Suggest an Idea button. Please submit one actionable idea per post rather than a single post with multiple ideas.
  3. Kudo & Comment Kudo ideas you like, and comment to add to an idea.
  4. Subscribe: Follow the status of ideas you like. Refer to status definitions to understand where an idea is in its lifecycle. (You are automatically subscribed to ideas you've submitted or commented on.)

We consider several factors when looking for what ideas to add to JMP. This includes what will have the greatest benefit to our customers based on scope, needs and current resources. Product ideas help us decide what features to work on next. Additionally, we often look to ideas for inspiration on how to add value to developments already in our pipeline or enhancements to new or existing features.

Choose Language Hide Translation Bar

Compare data tables function

We miss one useful function for comparison all columns of two data tables in JMP16.

Compare_data_tables.png

 

 

 

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?

2 Comments
Status changed to: Acknowledged

Hi @bdr_data_team, thank you for your suggestion! We have captured your request and will take it under consideration.

datadad
Level III

I was going to post this as a wish list item too. In JMP 16, when the columns differ, but the matching ones do not, the message back is "There is no difference in the data." This is very misleading and has resulted in us missing changes. The column matcher widget is not sufficient because the lines connecting columns can be complex and cannot even be seen for typical data sets (>20 columns say).