Creating 400 + records in table with poor performance

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