☑ cool new feature
☑ could help many users!
☑ removes something that feels like a „bug“
☐ nice to have
☐ nobody needs it
What inspired this wish list request?
As of v19, Tables/Update needs a lot of fine tuning:
Option 1:
duplicate columns will be added in addition to existing columns. Such columns have to be identified manually and removed afterwards.
If not, after a few updates a huge number of columns will accumulate.
Option2:
the user has to specify exactly which columns have to be added.
Maybe hundreds of columns ...
What is the improvement you would like to see?
A fancy new automatic mode: "add non-existing columns" *)
JMP will compare the columns in the source table with the existing columns
- if a column exists, it is not added.
- if a column doesn't exist, it gets added.
*)
- "add non-existing columns" in addition to none/all/selected:
- for "all", one could add a a checkbox:
don't add duplicates of existing columns.
Why is this idea important?
Often a user wants to add information from another table via Tables/Update
- He doesn't want to add hundreds of duplicates of columns which are already there in the table.
- He doesn't want to invest a lot of time to decide column by column if the column is already available or if the column is new.
