Before changing data
Check the app, table and workspace. Role, record access and the owning account subscription determine whether a change is allowed. Validation and approval rules still apply.
Create and edit
- Open the table and record form.
- Complete required fields and select lookup records.
- Save and read the result: an approval request is not an applied data change.
- Check the saved record in the table.
- Confirm the result rather than assuming a closed dialog means success.
Import a file
- Open Import for the target table and select a supported CSV or Excel file.
- Select the sheet where prompted and map source columns to fields.
- Review required values, dates, numbers and lookup matching in the preview.
- Choose unmatched-lookup handling only where offered.
- Run the import and read the imported/skipped/error results. Reconcile accepted rows before retrying.
Partial results and approvals
An import can accept some rows and reject others. Do not assume everything rolled back; repeating the file can duplicate accepted rows. Preserve the result and correct rejected rows first.
Some approval-controlled operations block import and direct you to a record form. Follow that path. Ordinary file imports do not promise to run record-created workflows for every row.
Export
Use available CSV/Excel export or a configured snapshot destination. Confirm whether the chosen interface exports a table, filtered records or an app snapshot. Check row counts, IDs, dates and calculated values.
A downloaded file is a copy; editing it does not automatically change the app. Do not assume an export includes attachment binaries, permissions or everything needed to restore the app.
Save failures
Read the exact validation/permission message. Check required fields, owning-account status and record allowance. After an uncertain response, check whether the record exists before repeating the action.