load

Load CSV data into a Dataverse entity

Usage

ppds data load [options]

Options

Long	Short	Type	Default	Description
--analyze		bool		Analyze mapping without loading data (preview which columns match)
--batch-size		int		Records per batch (default: 100)
--bypass-flows		bool		Bypass Power Automate flow triggers
--bypass-plugins		string		Bypass custom plugin execution: sync, async, or all (requires prvBypassCustomBusinessLogic privilege)
--continue-on-error		bool		Continue loading on individual record failures
--debug		bool		Enable diagnostic logging output
--dry-run		bool		Validate without writing to Dataverse
--entity	-e	string		Target entity logical name
--environment	-env	string		Override the environment URL. Takes precedence over profile's bound environment.
--file	-f	FileInfo		Path to CSV file
--force		bool		Force loading even when auto-mapping is incomplete (unmatched columns will be skipped)
--generate-mapping		FileInfo		Generate mapping template to specified file
--key	-k	string		Alternate key field(s) for upsert. Comma-separated for composite keys.
--mapping	-m	FileInfo		Path to column mapping JSON file
--output-format	-o	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.
--verbose	-v	bool		Enable verbose logging output