Actions35
- Adjustments Actions
- Assemblies Actions
- Batches Actions
- Companies Actions
- Contacts Actions
- Custom Fields Actions
- File Attachments Actions
- Inventory Actions
- Invoices Actions
- Locations Actions
- Orders Actions
- Packages Actions
- Payment Methods Actions
- Product POS Mappings Actions
- Products Actions
- Purchases Actions
- Strains Actions
- Test Results Actions
- Users Actions
Batches → Get Many
AI-generatedOverview
This node operation retrieves multiple batch records from the Distru API. It supports filtering and pagination to fetch specific batches based on criteria such as batch IDs, product ID, batch number, creation or update datetime ranges, and whether to include deleted records or cost information. This operation is useful for inventory management, tracking product batches, and integrating batch data into workflows.
Use Case Examples
- Fetch all batches for a specific product with pagination to handle large datasets.
- Retrieve batches created within a specific date range for reporting or auditing purposes.
- Include cost details in the batch data for financial analysis.
Properties
| Name | Meaning |
|---|---|
| Page Number | Page number for pagination to control which page of results to retrieve. |
| Page Size | Number of items per page to control the size of each page of results. |
| Inserted Datetime | Filter batches by their creation datetime using a comma-separated range (e.g., "2024-01-01T00:00:00Z,2024-06-01T00:00:00Z"). |
| Updated Datetime | Filter batches by their last modified datetime using a comma-separated range. |
| Batch IDs | Filter batches by specific batch IDs, allowing multiple values. |
| Product ID | Filter batches by a specific product ID. |
| Batch Number | Filter batches by batch number. |
| Deleted | Option to include deleted records in the response, with choices to exclude, include only deleted, or include all. |
| Include Costs | Boolean flag to include cost fields in the response. |
Output
JSON
json- Array of batch objects returned from the Distru API, each representing a batch with its details such as IDs, product association, batch number, timestamps, and optionally cost information.
Dependencies
- Requires an API token credential for the Distru API to authenticate requests.
Troubleshooting
- Ensure the API token credential is set correctly; otherwise, the node will throw an error indicating the token is not set.
- If the 'Resource ID' parameter is required for other operations but missing, the node will throw an error; for 'Get Many' operation, this is not required.
- If binary data is expected for other operations but missing, an error will be thrown; not applicable for 'Get Many'.
- Incorrect filter formats, especially for datetime ranges, may result in no data or errors from the API.