cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
JMP is taking Discovery online, April 16 and 18. Register today and join us for interactive sessions featuring popular presentation topics, networking, and discussions with the experts.
Choose Language Hide Translation Bar
jetpeach
Level II

Moving column group to 'after column' is only moving it to the first

​I'm trying something that seems simple - moving a column group to a location after another column.

 

Moving "to last" works, "to first" works, but after doesn't for me, no matter how i mess with format.

 

Below is example code to test -

 

Names Default To Here( 1 );
dt = Open( "$SAMPLE_DATA/Cities.jmp" );
dt << group columns( "xy", {:X, :y} );
dt << group columns( "pollutants", :Ozone :: :Lead );
dt << move column group( to first, "xy" );

this worked but if

 

dt << move column group( after("Latitude"), "xy" );

instead of the "to first"

 

then I get very strange behavior - BOTH the groups move the first location in the dt.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Moving column group to 'after column' is only moving it to the first

This thread is rather old, but in case anyone stumbles upon it, i would like to document that this issue was reported to our JMP Development team, and the issue was addressed in JMP 14. All the script lines in the original post which are marked "not working" are actually working now.

View solution in original post

3 REPLIES 3
txnelson
Super User

Re: Moving column group to 'after column' is only moving it to the first

Move Column Group does not have the "after" argument like  Move Selected Columns does.

However, you can select the group, and then use

     dt << Select Column Group("xy");

     dt << Move Selected Columns(after("?????"));

Jim
altug_bayram
Level IV

Re: Moving column group to 'after column' is only moving it to the first

I can confirm that your solution Jim does indeed work....

Re: Moving column group to 'after column' is only moving it to the first

This thread is rather old, but in case anyone stumbles upon it, i would like to document that this issue was reported to our JMP Development team, and the issue was addressed in JMP 14. All the script lines in the original post which are marked "not working" are actually working now.