Repository Movements

repositoryMovements Query

Returns a paginated list of RepositoryMovement objects, with optional filtering and ordering.

Arguments

Name	Type	Description
after	Cursor	Returns the elements in the list that come after the specified cursor
first	Int	Returns the first n elements from the list
before	Cursor	Returns the elements in the list that come before the specified cursor
last	Int	Returns the last n elements from the list
orderBy	RepositoryMovementOrder	Ordering options for RepositoryMovements returned from the connection
where	RepositoryMovementWhereInput	Filtering options for RepositoryMovements returned from the connection

Return Type

RepositoryMovementConnection! - A connection to a list of RepositoryMovement objects with pagination information.

Notes

The data field contains custom movement attributes as JSON. You can use the Data, DataHasKey, DataIn, and DataContains filters to query based on JSON content. For complex JSON field queries, see Advanced JSON Field Queries.

Usage Example

query {
  # Get pending repository movements
  repositoryMovements(
    where: { executed: false }
    orderBy: { field: CREATED_AT, direction: ASC }
    first: 10
  ) {
    edges {
      node {
        id
        repository {
          id
          name
          type
        }
        from {
          name
        }
        to {
          name
        }
        executed
        blockedBy
      }
    }
    totalCount
  }
}

query {
  # Get movements for a specific repository
  repositoryMovements(
    where: { 
      repositoryID: "pallet-123",
      executedAt_GTE: "2024-01-01T00:00:00Z"
    }
  ) {
    edges {
      node {
        id
        executedAt
        from {
          name
        }
        to {
          name
        }
      }
    }
  }
}

Common Filters

• executed - Filter by execution status

• repositoryID - Find movements for a specific repository

• fromID / toID - Filter by source or destination

• blockedBy - Find blocked movements

• collectionID - Find movements in a collection

• executedAt_GTE / executedAt_LTE - Filter by execution date range

Notes

• Repository movements track the relocation of dynamic repositories

• Use this to monitor pallet movements, tote transfers, etc.

• Movements must be executed to take effect

• Can be part of collection movements for batch operations