update

Update records in a Dataverse entity (fails if record doesn't exist)

Usage

ppds data update [options]

Options

Long	Short	Type	Default	Description
--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 updating on individual record failures
--correlation-id		string		Correlation ID for distributed tracing
--debug		bool		Show trace-level diagnostic output
--dry-run		bool		Preview records that would be updated without actually updating
--entity	-e	string		Target entity logical name
--environment	-env	string		Override the environment URL. Takes precedence over profile's bound environment.
--file		FileInfo		Path to CSV file containing records to update (must include ID column and columns to update)
--filter		string		SQL-like filter expression to match records for update (e.g., "statecode eq 0")
--force		bool		Skip confirmation prompt (required for non-interactive execution)
--id		Guid?		Record ID (GUID) to update
--id-column		string		Column name containing record IDs in CSV file (default: entity primary key)
--key	-k	string		Alternate key field(s) for lookup. Format: field=value or field1=value1,field2=value2 for composite keys.
--limit		int?		Maximum number of records to update (fails if query returns more)
--mapping	-m	FileInfo		Path to column mapping JSON file (for --file mode)
--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.
--quiet	-q	bool		Show only warnings and errors
--set	-s	string		Field values to set. Format: field=value or field1=value1,field2=value2. Required for --id, --key, or --filter modes.
--verbose	-v	bool		Show detailed output including debug messages