Import Access
Description
Section titled “Description”Reads a Microsoft Access database file from a document account and imports its tables — one project table per Access table, named with a prefix you choose.
Because an Access file holds many tables, this step imports the file as a whole rather than mapping a single table’s columns.
Unique Configuration Items
Section titled “Unique Configuration Items”Source
Section titled “Source”The Access database file in a document account. The file picker also supports matching by search rather than an exact path, with a recursive option and a rule for reconciling schema differences across matched files.
Target
Section titled “Target”Table prefix — prepended to each imported table’s name, so one file’s tables stay grouped and do not collide with another import’s.
Skip if Unchanged
Section titled “Skip if Unchanged”On by default. A workflow run skips the import entirely — download included — when the source file has not changed since the last run.
When the File Cannot Be Read
Section titled “When the File Cannot Be Read”The step fails, naming the file and the table it could not read, rather than finishing and leaving an empty table behind. That happens when the file lists no tables PlaidCloud can read, when a table is named but its columns cannot be described, or when reading a table’s rows fails — a file written by a newer version of Access than the reader understands is the usual cause. Convert or re-export the file from Access and run the import again.
A file whose tables are all genuinely empty imports successfully and reports a warning that no records were loaded.