pub struct MetadataComponentDependency {
pub metadata_component_id: Option<String>,
pub metadata_component_name: Option<String>,
pub metadata_component_namespace: Option<String>,
pub metadata_component_type: Option<String>,
pub ref_metadata_component_id: Option<String>,
pub ref_metadata_component_name: Option<String>,
pub ref_metadata_component_namespace: Option<String>,
pub ref_metadata_component_type: Option<String>,
}Expand description
MetadataComponentDependency represents dependency relationships between metadata components.
This type is available in:
- Tooling API (API version 43.0+) - up to 2000 records per query
- Bulk API 2.0 (API version 49.0+) - up to 100,000 records per query
§Example
use busbar_sf_client::MetadataComponentDependency;
// Query via Tooling API
let deps: Vec<MetadataComponentDependency> = tooling_client
.query_all("SELECT MetadataComponentId, MetadataComponentName, RefMetadataComponentId, RefMetadataComponentName FROM MetadataComponentDependency")
.await?;
// Query via Bulk API
let result = bulk_client
.execute_query(
QueryBuilder::new("MetadataComponentDependency")?
.select(&["MetadataComponentId", "MetadataComponentName"])
)
.await?;Fields§
§metadata_component_id: Option<String>The ID of a metadata component that depends on another component.
This is usually an 18-character ID or a standard object name. Use 18-character IDs (not 15-character IDs) in queries.
metadata_component_name: Option<String>The name of a metadata component that depends on another component.
For example, “YourClass” for an Apex class or “yourField” (without the __c suffix) for a custom field.
metadata_component_namespace: Option<String>The namespace of a metadata component that depends on another component.
metadata_component_type: Option<String>The type of a metadata component that depends on another component.
Examples: “ApexClass”, “CustomField”, “WorkflowRule”, etc.
ref_metadata_component_id: Option<String>The ID of a metadata component that another component depends on.
This is usually an 18-character ID or a standard object name. Use 18-character IDs (not 15-character IDs) in queries.
ref_metadata_component_name: Option<String>The name of a metadata component that another component depends on.
For example, “YourClass” for an Apex class or “yourField” (without the __c suffix) for a custom field.
ref_metadata_component_namespace: Option<String>The namespace of a metadata component that another component depends on.
ref_metadata_component_type: Option<String>The type of a metadata component that another component depends on.
Examples: “ApexClass”, “CustomField”, “StandardEntity”, etc.
Trait Implementations§
Source§impl Clone for MetadataComponentDependency
impl Clone for MetadataComponentDependency
Source§fn clone(&self) -> MetadataComponentDependency
fn clone(&self) -> MetadataComponentDependency
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more