batch Module
Batch operation namespaces for the Dataverse SDK.
Classes
| BatchDataFrameOperations |
DataFrame-oriented wrappers for batch record operations. Provides create, update, and delete that accept
Accessed via Example:
|
| BatchOperations |
Namespace for batch operations ( Accessed via Example:
|
| BatchQueryOperations |
Query operations on a BatchRequest. Mirrors Do not instantiate directly; use |
| BatchRecordOperations |
Record operations on a BatchRequest. Mirrors GA methods: retrieve (single record) and list (multi-record, single page). get is deprecated — use retrieve instead. Do not instantiate directly; use |
| BatchRequest |
Builder for constructing and executing a Dataverse OData Obtain via new ( Operations are executed sequentially in the order added. The resulting BatchResult contains one BatchItemResponse per HTTP request dispatched (some operations expand to multiple requests). Note Maximum 1000 HTTP operations per batch. Example:
|
| BatchTableOperations |
Table metadata operations on a BatchRequest. Mirrors Note tables.delete, tables.add_columns, and tables.remove_columns require a metadata lookup (GET EntityDefinitions) at execute time to resolve the table's MetadataId. This lookup is transparent to the caller. Note tables.add_columns and tables.remove_columns each produce one batch item per column, so they contribute multiple entries to Do not instantiate directly; use |
| ChangeSet |
A transactional group of single-record write operations. All operations succeed or are rolled back together. Use as a context
manager or call Do not instantiate directly; use changeset. Example:
|
| ChangeSetRecordOperations |
Record write operations available inside a ChangeSet. Mirrors Do not instantiate directly; use |