Actions32
- Resource Actions
- Work Order Actions
- Work Order Routing Actions
- Work Order Pos Actions
- Work Order BOM Actions
- Reservation Actions
- Time Receipt Actions
- Item Actions
Item → Get All
AI-generatedOverview
This node interacts with the BEAS Service Layer API to retrieve multiple records of the 'Item' resource. It supports filtering, sorting, pagination, field selection, and expansion of related entities using OData query parameters. This is useful for scenarios where you need to fetch a list of items with specific criteria, such as filtering items by status or creation date, sorting them by a field, or limiting the number of records returned.
Use Case Examples
- Fetch all items created after a certain date, sorted by creation date descending.
- Retrieve the top 10 items with a specific status, selecting only certain fields like ItemID and Description.
- Get all items and expand related entities such as item categories or suppliers.
Properties
| Name | Meaning |
|---|---|
| Filters | OData filter string to filter the items based on conditions (e.g., Status eq 'Open' or CreationDate ge '2024-03-20'). |
| Sort | OData sort string to order the items by specified fields (e.g., CreationDate desc or Status asc). |
| Skip | Number of records to skip for pagination purposes. |
| Top | Maximum number of records to return. |
| Select | Comma-separated list of fields to select in the response. Leave empty to get all fields. |
| Expand | Comma-separated list of related entities to expand in the response. Leave empty for no expansion. |
Output
JSON
json- The JSON response containing the list of items retrieved from the BEAS Service Layer API, including any selected fields and expanded related entities.
Dependencies
- BEAS Service Layer API with valid credentials including service URL and service password for authentication.
Troubleshooting
- Ensure the service URL and service password credentials are correct and valid to obtain a session cookie; failure to get the session cookie will cause the node to throw an error.
- Invalid OData filter, sort, select, or expand strings may cause the API request to fail; verify the syntax and field names used in these parameters.
- If the JSON response is empty or incomplete, check the 'Top' and 'Skip' parameters to ensure correct pagination.
- If the node throws an error about unsupported operations or resources, verify that the resource is set to 'Item' and operation to 'Get All'.