Ahhhhh right that would be the problem. There IS a limit on 20 actions when editing via an inline form.
Is there a reason why you want to do data upload via an inline form specifically?
If it was completely up to me here is how I would orchestrate this upload process:
- Create an ontology object called “CSV upload” or something similar
- Use the Media Uploader widget that will take the CSV and upload it to a Media Set
- Upon the successful upload, run an action to create a new “CSV upload” object and set the media reference property to the “Uploaded File” in the Media Uploader widget configuration (see notional configuration in image below)
- Trigger an automation that runs on all newly created “CSV upload” to parse the CSV file in the media reference property and create new ontology objects
Please let me know if that would work in your use case / if you need any further clarification
