It’s not always appropriate, but you can set the model to be processed client side, which will delay loading of data and metadata until the page has finished loading. This will cause a “requery” event as soon as the page has finished loading, which gives you the ability to set an action on the first load of data.
This is not ideal, but it can work in limited situations until something more comprehensive is available.
Thanks. I didn’t understand what the client side processing really did, but it’s beginning to make sense.
Just checking in here, I think what you’re doing would now be possible through an Event-Triggered Action Sequence on the “Skuid Page: Rendered” event? (https://docs.skuid.com/latest/en/skuid/action-framework/action-sequences/#event-triggered-sequences)