It would be helpful for app creators to have more options within the App: import a CSV file for this view action to control the actions behavior. This would help avoid user errors and even inappropriate (whether malicious or unintentional) revisions to existing rows or population of columns intended to be excluded from the import. For example:
- A property that governs whether the action will only add rows, only update existing rows, or both (e.g., so I can prevent users from editing existing rows)
- A property that governs which columns will be imported from the .csv file (e.g., so I can prevent users from including columns I don't want populated via import)
- Properties that govern mapping from .csv file column headers to column names in the AppSheet table (e.g., so I can give users a template with user-friendly column headers that map to column names within the app)