SaveToDataSet 1.0.0¶

Overview¶

Data Beginner

v1.0.0 Native

Description¶

Saves a single item with specified properties to a specific dataset identified by ID.

Configuration Options¶

Name	Data Type	Description	Default Value
dataset_id	`UUID`	Target dataset ID where the item will be saved. Must be a valid UUID format	Required

Inputs¶

Name	Data Type	Description
**properties	`Any`	Arbitrary properties to save as a dataset item. Can include id (UUID), custom fields, and any structured data

Outputs¶

No outputs available.

Examples¶

# Save data to specific dataset by ID
steps:
  - name: save_to_specific_dataset
    block: SaveToDataSet
    config:
      dataset_id: "550e8400-e29b-41d4-a716-446655440000"
    title: "Customer Analysis Report"
    content: "Customer satisfaction has improved by 23% this quarter..."
    metrics:
      satisfaction_score: 4.2
      response_rate: 0.78

    

# Save processed data to different datasets based on content type
steps:
  - name: analyze_content
    block: LLMDataEnrich
    input_data: "Categorize this content as either 'financial', 'technical', or 'marketing'"

  - name: save_financial
    block: SaveToDataSet
    config:
      dataset_id: "finance-dataset-uuid"
    condition: "{analyze_content.output} == 'financial'"
    document_type: "financial_report"
    processed_content: "{analyze_content.output}"

  - name: save_technical
    block: SaveToDataSet
    config:
      dataset_id: "technical-dataset-uuid"
    condition: "{analyze_content.output} == 'technical'"
    document_type: "technical_doc"
    processed_content: "{analyze_content.output}"

    

# Save results from batch processing
steps:
  - name: process_documents
    block: Map
    items: "List of document IDs to process"

  - name: save_batch_results
    block: SaveToDataSet
    config:
      dataset_id: "batch-results-dataset-uuid"
    batch_id: "batch_2024_03_15_001"
    processed_items: "{process_documents.results}"
    total_processed: 150
    success_rate: 0.96
    processing_date: "2024-03-15T16:45:00Z"

    

Error Handling¶

Invalid Dataset ID

Error Code: invalid_dataset_id
Common Cause: Dataset ID is null, malformed, or does not exist in the workspace
Solution: Verify dataset ID is a valid UUID and exists in the current workspace. Check dataset permissions

Workspace Access Required

Error Code: workspace_required
Common Cause: Block is used outside of a workspace context
Solution: Ensure block runs within a proper workspace context with access to the target dataset

Dataset Write Permissions

Error Code: permission_denied
Common Cause: User lacks write permissions to the specified dataset
Solution: Verify user has appropriate write access to the target dataset. Check dataset permissions and user roles

FAQ¶

How do I find the correct dataset_id?

Dataset IDs are UUIDs that can be found in your workspace dataset list, API responses, or retrieved using dataset management tools. They uniquely identify each dataset within your workspace.

What's the difference between Save and SaveToDataSet?

Save operates within the current dataset scope context, while SaveToDataSet allows explicit targeting of any dataset by ID. Use SaveToDataSet for cross-dataset operations or when dataset context is not available.

Can I save to multiple datasets simultaneously?

Each block instance targets one dataset. To save to multiple datasets, use multiple SaveToDataSet blocks with different dataset_id configurations, or iterate with a Map block.

How does ID handling work?

The block looks for id, ID, or Id properties in your data. If found, it validates the UUID format. If no valid ID is provided, a new UUID is automatically generated for the dataset item.

Are there dataset size or item limits?

Dataset capacity depends on your workspace configuration and subscription plan. The block handles individual item saves efficiently, but large batch operations may benefit from chunking strategies.