schema
Generate a migration schema from Dataverse metadata
Usage
ppds data schema [options]
Options
| Long | Short | Type | Default | Description |
|---|---|---|---|---|
--debug | bool | Enable diagnostic logging output | ||
--disable-plugins | bool | Set disableplugins=true on all entities | ||
--entities | -e | String[] | Entity logical names to include (comma-separated or multiple -e flags) | |
--environment | -env | string | Override the environment URL. Takes precedence over profile's bound environment. | |
--exclude-attributes | String[] | Exclude these attributes (blacklist, comma-separated) | ||
--filter | String[] | SQL-like filter per entity. Format: entity:expression (e.g., "account:statecode = 0"). Repeatable. | ||
--include-attributes | -a | String[] | Only include these attributes (whitelist, comma-separated or multiple flags) | |
--include-audit-fields | bool | Include audit fields (createdon, createdby, modifiedon, modifiedby, overriddencreatedon) | ||
--output | -o | FileInfo | Output schema file path | |
--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. | |
--verbose | -v | bool | Enable verbose logging output |