Seems like server side would be better.

Trying to better understand the comment above. Will just moving the save from the skuid page to an apex class perform better? I would still have to figure out how to pass the records from the skuid page to the apex class. Or was the suggestion that all 400 loop processing and save be moved to the apex class?

I just think that the solution you’ve to built to save 400+ records in Skuid is unlikely to be without issues. Salesforce isn’t able to accommodate saving so many records in one operation from a user. So, you could setup your snippet to save in smaller batches of records, but then you’d be opening up the solution to other issues. What would happen if the internet connection was lost of the browser crashed in the middle of saving some records. You’d a partially saved set of records. How would you recover from that? This is why it would be best to build this solution server side. Process and Flow? Apex? Dunno

Eric,

This seems like a good use for @invocable Apex.  You can have your user select the parameters and pass them into the invocable call through the Action Framework.  With 400+ records to create, you want Salesforce to handle this.

Thanks,

Bill