cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • JMP 19 is here! See the new features at jmp.com/new.
  • Register to attend Discovery Summit 2025 Online: Early Users Edition, Sept. 24-25.
Choose Language Hide Translation Bar
hogi
Level XII

Tables/Update changed!

Please note, there is a significant change of the Tables/Update functionality in JMP19.

dt = Open( "$SAMPLE_DATA/Big Class.jmp" );
dt = Open( "$SAMPLE_DATA/Big Class Families.jmp" );


// Update data table
Data Table( "Big Class" ) << Update(
	With( Data Table( "Big Class Families" ) ),
	Match Columns( :name = :name, :age = :age ),
	Replace Columns in Main Table( None )
);

 

Available columns after executing the script 1x, 2x  and 3x in JMP18 *):

hogi_0-1758194509286.png  hogi_0-1758194509286.png    hogi_0-1758194509286.png 
*) after adding new columns in the first step, no new columns are added. JMP informs the user:
     hogi_1-1758194530906.png

 

 

Available columns after executing the script 1x, 2x  and 3x with JMP19:

hogi_2-1758194584719.png  hogi_3-1758194609797.png  hogi_4-1758194913065.png

 

 

The new feature seems to be triggered by this post in the Wish List:

Allow Update platform to create new columns if they already exist in the table to be updated 

This wish is great, as an option - but it might collide with how other users used Tables/Update up to now.
Especially dangerous if scripts are affected.

Can the new functionality be disabled?

0 REPLIES 0

Recommended Articles