import

Import data from a ZIP file into Dataverse

Usage

ppds data import [options]

Options

Long	Short	Type	Default	Description
--bypass-flows		bool		Bypass Power Automate flow triggers (no special privilege required)
--bypass-plugins		string		Bypass custom plugin execution: sync, async, or all (requires prvBypassCustomBusinessLogic privilege)
--continue-on-error		bool		Continue import on individual record failures
--data	-d	FileInfo		Path to data.zip file
--debug		bool		Enable diagnostic logging output
--environment	-env	string		Override the environment URL. Takes precedence over profile's bound environment.
--error-report		FileInfo		Base path for output files (creates .errors.jsonl, .progress.log, .summary.json). Errors are streamed in real-time.
--impersonate-owners		bool		Preserve record ownership via CallerAADObjectId impersonation (requires --user-mapping)
--mode	-m	ImportMode		Import mode: Create, Update, or Upsert
--output-format	-f	OutputFormat		Output format
--profile	-p	string		Profile name(s). For high-throughput pooling, specify multiple Application User profiles comma-separated (e.g., app1,app2,app3) - each profile multiplies API quota.
--resolve-lookups		bool		Enable external lookup resolution (ID check, then name-based query)
--skip-missing-columns		bool		Skip columns that exist in exported data but not in target environment (prevents schema mismatch errors)
--skip-unresolved-lookups		bool		Null unresolved lookups instead of failing the record [default: True] (requires --resolve-lookups)
--strip-owner-fields		bool		Strip ownership fields (ownerid, createdby, modifiedby) allowing Dataverse to assign current user
--user-mapping	-u	FileInfo		Path to user mapping XML file for remapping user references
--verbose	-v	bool		Enable verbose logging output