Work with CRD Bursting Schedules

The CRD API Reference lists three operations for bursting schedules: retrieve report columns, retrieve group values, and create a bursting schedule. This guide follows that sequence and leaves request details to the operation schemas, which define the required fields for your installation.

Before you begin

Authenticate with the CRD API. See Authentication and Token Management.
Identify the report and schedule context required by the bursting operations. Use the exact identifiers and field names shown in the API Reference.
Review the individual request schemas before sending a request. Do not reuse a single-report or package request body for a bursting operation.

Follow the reference workflow

Inspect the report columns. Use GetReportColumns to retrieve the available columns for the report context described by that operation.
Retrieve group values. Use GetGroupValues with the fields specified by its reference. The operation reference defines how to identify the report and column and what response to expect.
Create the bursting schedule. Submit CreateBurstingSchedule using its documented request schema. Check its response before proceeding.

Keep request models separate

The three operations have different purposes and request schemas. Use the report and group-value responses as inputs only where the create operation's documented fields call for them. The API Reference is authoritative for valid values, required identifiers, and response fields.

Do not infer schedule fields from a different CRD schedule type, and do not assume the create operation returns a reusable schedule identifier unless the response schema documents one. If the request fails, check the operation's required fields and the error response before retrying.

Related guides

Create and Maintain Single-Report Schedules covers single-report schedule operations.
Monitor, Recover, and Reconcile Executions covers execution monitoring.
Browse the CRD API Reference for the exact method, path, authentication, parameters, request body, and responses for each operation.