Multi-Select capabilities

There have been numerous requests for this already so I think it's time TimeXtender bit the bullet and implemented this. From what I understand, this means a lot of reprogramming work because of the UI component used but it would make a lot of users happy so it's definitely worth it.

I suggest all TX users active here post their use cases for multiselect :). Here are ours:

- Multiselect a number of tables to be executed for example

- Multiselect a number of data movements in the DW to remove them.

- Multiselect a number of dimension members to delete them

- Multiselect a number of fields in the custom view editor and drop them in the editor to create parameters

- The same for the custom SQL editor

- Multiselect a number of execution packages and reorder them

- Multiselect relations or relation folders and delete them

- Multiselect a number of tables or views in the stage and drop them on the DW

- Multiselect a number of fields in the source to deselect or select them for the stage

Even just a "select all" shortcut would be a huge improvement, but multi-select would be very useful!

Ability to multi-select tables to set common Table Settings such as performance options.  Set Batch Data Cleansing, Compression options, Physical Valid Table, etc.

I just did that manually for about 200 tables, and my hand may fall off  :)

Sorry to hear about your hand! But it's nice that we are fitted with a spare one. :)

Our problem with multi select is that we have a hard time to multi select in trees and make sensible decisions on all levels. The real-world examples of successful implementations are limited (I would like if you guys could provide us with them if you find them). The hard part is that we have different objects on different levels - so a multi select isn't focused to a single object type (e.g. tables) but could span multiple types that isn't conform to the action that you want to perform. That's probably why nobody has done this before with success.

But we are very open to constructive suggestions - we have tried very hard but always end with the only option to switch from hierarchies 

I have already given input but we're turning in circles for years on this it seems.

One very simple multiselect I would appreciate is moving multiple tables at once, or multiple fields withing one table and having the option of sorting them.

Another would be to select all datamovements in a DW table and delete all of them at once (when for example you have accidentally dropped the wrong stage table on the wrong dw table).

Multiselect all fields in the custom SQL editor to add them as parameters etc...

1. Multiselect tables and enabled guard.
2. Multiselect tables and put them to SCD type 1
3. Multiselect tables and execute or deploy
4. Add multipe dimensions to a cube
5. Creating a custom view, select multiple fields and add them.
   Also allow the use of custom sorting your tables in this window. If you have 200+ objects it's a pain to find the right table. (this feature has been requested multiple times as well)

It would even fit perfectly with the TX philosophy of doing more with less actions.

I agree with Raf. The view editor could use some much needed love.

Thanks for your suggestions.

But would you please help us out with real world examples of succesful implementations of multi select in OTHER applications with the following constraints:

• Hierarchy oriented panel
• Different types of objects on same and different levels
• Different actions possible on different objects

The problem is that when an hierarchy is used in an application - multi select is just not intuitive from a user perspective and poses a complex programing task to sort out the users intent.

If you look to other Microsoft implementations - eg. Windows File Explorer, Office Outlook or SSMS Object Explorer - multi select is never implemented in the hierarchy. It is always accompanied by another pane where you are working in a list view of the current node in the hierarchy. It is only in list panes multi select is enables - eg. the files in the selected folder, The mails in the current mailbox or script in the Query editor.

The only hierarchy multi select you see is normally just for selection the same type of objects in dropdowns like Excel, Pivot filter selectors or in Java Applications where you implement checkboxes in front of all nodes and leaves in the hierarchy.

So examples, Gentlemen! - or we will have to wait for the planed revision of the interface where we are working on preserving the simplicity and ease of the current hierarchy combined with the speed of bulk operations in multi select.

I can not think of an example within those constraints, I would like to see "select all" and similar capabilities for the lists when selecting fields for type 2 history for instance.

Jan,

I think I see what you're referring to.  What about restricting multiselect to a single level of the tree hierarchy.  Once the first item is selected in the project tree, only others at that same level can be selected.  

I've seen features implemented in other products for changing properties on multiple items at the same time.  Lets say we select several tables and would like to modify Table Settings for all.  Ideally, it should only enable items which are in common across the selected tables.  So if a table selected is of a different type and doesn't allow for a certain property to be modified, it should be disabled (greyed out) in the Multi-select Table Settings.

Does this help?   I can work on some more examples.  

Thanks David for the input.

I think that the idea of using the tree hierarchy to restrict the level and then some way of aligning the selection list - perhaps something like a cross of the shift-ctrl-f Find Window with a object filter and added an action panel. Hmmm.

I think we should try to bring that to the next feature grooming session.

Some of the other places in TX, you guys have mentioned, like the field chooser in custom views, I simply just thing that we should flatten out so that ordinary list selection becomes an option - but I am probably going to have a bit of work finding a new UX strategy that covers all the places where we need to drop that in.

But thanks for the input. It feels like we might have something for the main tree hierarchy that isn't going to be shoot down at the first presentation.

+1

1. Multiselect fields and do the same data transformation

2. Multiselect fields and delete them

Jan,

I just realised I do know a multiselect tree structure program.

The music player Foobar2000 https://www.foobar2000.org/ has a tree structure object where you can multi-select nodes and leafs and apply actions on them.

So if these guys can do it, I'm sure our TX guys are also capable :).

KR,

Wim

Thank you, Wim. We will look into Foobar2000 and see what we can learn from it. 

Just had a another partner request in this area. I have have these request from customer/partners quite often - any news/progress? 
Have a look at Wim's post above - is seems like a tree-structure isn't necessary an obstacle here ....

Would be a great feature to change the table settings for multiple similar tables!

@Jan, is this still being looked at?

Yes we are looking. But not much have changed, so it's still a quit difficult to implement in a way that will be intuitive and functional.

When multi select is hard because of the hiearchy, you could try to "reverse" the process. For example when opening the table settings on a single table, you could then add a new tab inside the table settings which shows all tables so the user can select all tables to apply it to. (where the initial selected table is allready enabled).

This week I had to enable SCDTypeII on thousands of columns accross many tables, in that box (like Rory Smith allready mentioned), the multi (or all) select box should be a simple one to add.

The history settings:

The datasource settings:

Hi David, 
Thanks for submitting your ideas. Your continued feedback on our product is very important to us.

As you can see from the many comments on this post, Multi-Select in a Tree structure interface presents a unique set of challenges. We have made some improvements in this area which you can see reflected in the various "Automate" and other wizards throughout. We will continue to evaluate how we can improve upon selecting and editing multiple objects in TimeXtender in future versions. 

If you have any questions or would like to discuss further, please reach out to me or the dedicated TimeXtender Solution Specialist in you region. Thanks!

Is there any update on multiselecting and multidragging Tables and fields in the Tree?