Multi-Operation Requests

One of Dynomate's most powerful features is its ability to chain multiple DynamoDB operations together in a single request. This allows you to create complex workflows that would otherwise require custom code or multiple separate requests.

Creating a Request

To create a new multi-operation request:

1. Navigate to the "Requests" or "Collections" panel in the Dynomate interface
2. Click the "New Request" or "+" button to create a new request
3. Give your request a descriptive name

Adding Operations

Each request can contain multiple DynamoDB operations. To add an operation:

1. In your request, click the "Add Operation" button
2. Select the operation type (Query, Scan, GetItem, PutItem, UpdateItem, DeleteItem)
3. Configure the operation settings:

You can add as many operations as needed, and they will be executed in sequence when you run the request.

Referencing Previous Operations

The real power of multi-operation requests comes from the ability to reference the results of previous operations in subsequent operations. This allows you to create dynamic workflows that would otherwise require custom code.

Reference Syntax

To reference a value from a previous operation, use the following syntax:

${operation_name.path.to.value}

Where:

• operation_name is the name of the previous operation
• path.to.value is the path to the value in the result object

Example: User and Orders

Here's a common example of using operation references:

{ 
  "operation": "query",
  "table": "Users",
  "keyCondition": "email = :email",
  "expressionValues": {
    ":email": "user@example.com"
  }
}

{
  "operation": "query",
  "table": "Orders",
  "keyCondition": "userId = :userId",
  "expressionValues": {
    ":userId": "${get_user.items[0].userId}"
  }
}

Request Logs

As your multi-operation requests execute, Dynomate provides detailed logs of each operation, including:

• The raw request data sent to DynamoDB
• Any parameters used (like keys, filters, or expression attributes)
• The results returned from DynamoDB
• Timing information for each operation

These logs are invaluable for debugging complex requests and understanding exactly what data is being sent to and received from DynamoDB.

Saving Requests

Once you've created a multi-operation request, you can save it for future use:

1. Click the "Save" button in the request editor
2. Choose a collection to save the request in (or create a new collection)
3. Optionally add a description or tags to help organize your requests

Advanced Examples

Data Migration Flow

This example shows how to create a multi-operation request that migrates data from one table to another, with transformation:

// Operation 1: Get source data
{
  "name": "getSourceData",
  "operation": "scan",
  "table": "OldUsers",
  "limit": 10
}

// Operation 2: Transform and insert into new table
{
  "name": "transformAndInsert",
  "operation": "batchWrite",
  "table": "NewUsers",
  "items": [
    "#each get_source_data.items as |user|": {
      "newId": "${user.id}",
      "fullName": "${user.firstName} ${user.lastName}",
      "email": "${user.email}",
      "createdAt": "2025-05-01T09:37:39.522Z"
    }
  ]
}

Conditional Update Chain

This example demonstrates a conditional update that only executes if certain conditions are met:

// Operation 1: Check item status
{
  "name": "checkItem",
  "operation": "getItem",
  "table": "Orders",
  "key": { "orderId": "order-123" }
}

// Operation 2: Update if status is "pending"
{
  "name": "updateIfPending",
  "operation": "updateItem",
  "table": "Orders",
  "key": { "orderId": "order-123" },
  "updateExpression": "SET status = :newStatus, updatedAt = :timestamp",
  "conditionExpression": "status = :pendingStatus",
  "expressionValues": {
    ":newStatus": "processing",
    ":timestamp": "${new Date().toISOString()}",
    ":pendingStatus": "pending"
  },
  "skip": "${check_item.item.status !== 'pending'}"
}