set-fetchxml
Apply a complete FetchXML document to a view, replacing the existing fetchxml.
Expected format (file must have <fetch> as root element): <fetch version="1.0" output-format="xml-platform" mapping="logical" no-lock="false"> <entity name="account"> <attribute name="name" /> <order attribute="name" descending="false" /> <filter type="and"> <condition attribute="statecode" operator="eq" value="0" /> </filter> </entity> </fetch>
Usage
ppds views set-fetchxml [options]
Options
| Long | Short | Type | Default | Description |
|---|---|---|---|---|
--correlation-id | string | Correlation ID for distributed tracing | ||
--debug | bool | Show trace-level diagnostic output | ||
--entity | string | [Required] Entity logical name (e.g., account) | ||
--environment | -e | string | Override the environment URL. | |
--fetchxml | string | [Required] Path to a file containing a complete FetchXML document with <fetch> root element. | ||
--output-format | -f | OutputFormat | Output format | |
--profile | -p | string | Authentication profile name | |
--publish | bool | Publish the entity after the operation | ||
--quiet | -q | bool | Show only warnings and errors | |
--solution | string | Add the view to this solution after the operation | ||
--verbose | -v | bool | Show detailed output including debug messages | |
--view | -v | string | [Required] View name or ID |