Common questions about Import Sync Data usually focus on field recognition, sync choices, and append rules; the answers below help you troubleshoot quickly.
FAQ
What should I do if some field types are recognized incorrectly after import?
- After the import is complete, open the relevant field management area and review the field types.
- Change any field type that does not match your expected result.
- Before the next import, keep the data format in each column as consistent as possible.
Why was appended data not written as expected?
- Check whether the column names in the imported file exactly match the column names in the current multi-dimensional table.
- Confirm that the data you want to import is located in the first sheet of the file.
- If needed, download the standard template, reorganize the data by that structure, and import again.
When should I use data sync instead of a one-time import?
- If you only need to bring the current data into the target multi-dimensional table once, use a one-time import.
- If the target table needs to stay updated with future source changes, enable data sync when importing from another multi-dimensional table.
- Before enabling sync, confirm the source view and target scope to avoid syncing the wrong data.
Glossary
| Term | Definition |
|---|---|
| Multi-dimensional table | A table-based collaborative workspace for structured data that supports import, sync, and append operations. |
| Data sync | A relationship created during import that keeps the target data updated with changes from the source. |
| Append import | A way to add new data to the current table while keeping the existing records in place. |
| Standard template | An import template used to standardize column names and data structure so import issues are less likely. |