I suggest checking out this blog post for the complete front end and back end code for moving values between two multiselect picklists.

http://salesforce-shruthi.blogspot.com/2011/09/multiselect-picklist-solution-for.html

The rerenders should speed up the process by making each click an AJAX call out instead of a page reload, but having to go back-and-forth with the controller can still be a bit slow. I guess the best way to speed up the process is to avoid all the calls to the server and do everything in JavaScript / JQuery. I found an easy JQuery script from this blog for transporting between two select lists:

http://blog.jeremymartin.name/2008/02/easy-multi-select-transfer-with-jquery.html

When you’re ready to save your changes to the server, you’re probably going to have to create a javascript function to gather the values on both of the lists and then pass those values to the controller by a remote function.

Hope this helps.

Looking the functionality is good, no code is available to test your functionality. Please provide your code I will test in my dev account. It will be helpful if you post or send your code.

Thanks
Sreenath

Also- I am not really supposed to mention this (oh well) but we are releasing a new Application within the upcoming months that will allow you to sync your Content offline. We’ll have more info about this soon, so be sure to check our blog frequently for updates!

Hope this helps

Thanks.

I have build such a multi select box in Apex using action support, meaning each button click fires a request and the two lists are modified on the server. Problem: its damn slow. I could not firgure out how to elegantly built this in Javascript alone. So would you mind giving sharing your Javascript?

I would really love to implement it your “way”.

Best regards,

Robert

I tried changing the del to and that has returned the error:
BatchSchedule__c bdel = BatchSchedule__c.getOrgDefaults();
System.abortJob(bdel.scheduled_id__c);

Can you advise on how to do this across more than 2 batches? Thanks

We can infact delete the scheduled batch from the Schedulable class itself without need to store the batchId in custom settings.

In the Schedulable which has been scheduled using apex code, you can use the following code in the execute method to abort the job after executing the batch job as follows:

global class ScheduleBatchJob implements Schedulable {
global void execute(SchedulableContext SC) {

database.execute(batchClass, 200);
system.abortJob(sc.getTriggerId());
}
}

You also have to set an Default Organization Level Value on that Custom Setting. From the BatchSchedule__c details screen, click “Manage”, then the top “New” button above the Default Organization Level Value section, then save the defaults.

I’ll edit the post to include this extra step.