Well, dunno if you actually need actions when you can use jquery blockUI. Does the same Block and Unblock from Action Framework.
http://malsup.com/jquery/block/

So before skuid.model.updateData use jquery blockUI and instead of console.log, use the unblockUI.

As an example snippet:

var params = arguments[0], ActiveMSAs = skuid.$M('ActiveMSAs'), MSAServiceOrders = skuid.$M('MSAServiceOrders'), SOLineItems = skuid.$M('SOLineItems'), models = [SOLineItems,MSAServiceOrders,SOLineItems], $ = skuid.$; var dfd = $.Deferred(); $.blockUI({ message: 'Updating ...' }); $.when(skuid.model.updateData(models)) .done(function(){ $.unblockUI(); dfd.resolve(); }) .fail(function(){ $.blockUI({ message: 'Waiting...', timeout: 5000 }); dfd.reject(); }); return dfd.promise();<br>

Why do you add additional wait time on the failure? Why not just unblockUI and reject the promise?

No reason really. Don’t know where I copied this from.

Thanks. Was wondering because I’ve had some issues getting BlockUI to interact nicely between snippets and the action framework.

I haven’t had any issues. Have you been using $.Deferred()?

Yes, it was a while back actually. It might have been solved, I can’t remember. I’ll hit this thread again if I see the issue outright.

Thank you for that info Pat

Seems to work but for some reason it’s not unblocking when Models Querying is finished

Probably has to do with me not adapting your code to my scenario properly… 

As it’s over 550 lines, here’s just the end part, which contains the querying and your code, hopefully someone can spot my problem

var dfd = $.Deferred(); $.blockUI({ message: 'Updating ...' }); // query models with conditions set skuid.model.updateData(.myModel1,myModel2,myModel3,myModel5,myModel6,myModel7,myModel8,myModel9,myModel10,myModel12,myModel13,myModel14,myModel5,myModel6,myModel17,myModel18,myModel7,myModel19,myModel20,myModel21,myModel22,myModel23,myModel24,myModel25,myModel28,myModel29,myModel30,myModel31,myModel32,myModel33,myModel34,myModel35],function(){ console.log('update data complete!'); $.when(skuid.model.updateData(models)) .done(function(){ $.unblockUI(); dfd.resolve(); }) .fail(function(){ $.blockUI({ message: 'Waiting...', timeout: 5000 }); dfd.reject(); }); return dfd.promise(); });<br>

Just a quick reading … looks like you don’t unblock the UI when the function fails. You actually block the UI again.

 Also, I’m not sure if models1-35 is the same as the variable models, but if it is, then each time you update those models, it will run an update against the models again when the line

$.when(skuid.model.updateData(models))... 

executes which may be overkill depending on your situation.

You had it exactly Right, I did not realize it was duplicating the updatemodels.

I removed my line which was extra, and entered the proper models in pat’s line.

In case someone needs it here it is:

var dfd = $.Deferred(); $.blockUI({ message: 'Updating ...' }); $.when(skuid.model.updateData(amyModel1,myModel2,myModel3,myModel5,myModel6,myModel7,myModel8,myModel9,myModel10,myModel12,myModel13,myModel14,myModel5,myModel6,myModel17,myModel18,myModel7,myModel19,myModel20,myModel21,myModel22,myModel23,myModel24,myModel25,myModel28,myModel29,myModel30,myModel31,myModel32,myModel33,myModel34,myModel35])) .done(function(){ $.unblockUI(); dfd.resolve(); }) .fail(function(){ $.blockUI({ message: 'Waiting...', timeout: 5000 }); dfd.reject(); }); return dfd.promise();

Thx!

You may also want to change the message in the fail function because right now if the updates fail the ui will be blocked again and will say ‘Waiting…’