10,730
edits
Important: Deprecating old WebView — Publish failed error
Admin Console: Difference between revisions
Jump to navigation
Jump to search
→Importing entity records
| Line 49: | Line 49: | ||
# The import confirmation screen displays a list of records that will be created or updated. | # The import confirmation screen displays a list of records that will be created or updated. | ||
#* Select the proper '''Code page''' and '''Delimiter''' that match your CSV file. | #* Select the proper '''Code page''' and '''Delimiter''' that match your CSV file. | ||
#* Select one of the fields as the '''Primary key'''. The import will process the rows one by one and either create the records or update them | #* Select one of the fields as the '''Primary key'''. The import will process the rows one by one and either create the records - or update them if the primary key value matches an existing record in the database. Set the primary key to "<None>" and don't import the ID field to ensure that new records are created. | ||
#* In the preview table, select which columns to import into which entity fields. | #* In the preview table, select which columns to import into which entity fields. | ||
# Click '''Save'''. | # Click '''Save'''. | ||
For Note (annotation) entity | For Note (annotation) entity and also other custom entities with binary attachments, you can also import the documents (e.g., images). These can be either base64-encoded and included directly in the CSV, or you can import a ZIP file with one CSV and the individual documents. In this case, the CSV should contain the correct file name in the document field, instead of the base64 content. | ||
== Entities == | == Entities == | ||