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
Work Order Pos → Get All
AI-generatedOverview
This node interacts with the BEAS Service Layer API to retrieve all records of the 'Work Order Pos' resource. It supports filtering, sorting, pagination, field selection, and expansion of related entities using OData query parameters. This is useful for scenarios where users need to fetch multiple work order position records with specific criteria, such as filtering by status or sorting by creation date.
Use Case Examples
- Retrieve all work order positions with status 'Open' and sort them by creation date descending.
- Fetch the first 50 work order positions, selecting only specific fields like WorkOrderID and Description.
- Get all work order positions and expand related entities like WorkOrderLines for detailed information.
Properties
| Name | Meaning |
|---|---|
| Filters | OData filter string to filter the records, e.g., Status eq 'Open' or CreationDate ge '2024-03-20'. |
| Sort | OData sort string to order the records, e.g., CreationDate desc or Status asc. |
| Skip | Number of records to skip for pagination. |
| 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 work order position records retrieved from the BEAS Service Layer API.
Dependencies
- BEAS Service Layer API credentials including URL and service password for authentication.
Troubleshooting
- Ensure the BEAS Service Layer API credentials are correctly configured and valid.
- Verify the OData filter and sort strings are correctly formatted to avoid API errors.
- If the node fails to get a session cookie, check the service password and API URL.
- Invalid JSON errors may occur if the input JSON for POST or PATCH operations is malformed, but this is not applicable for the 'Get All' operation.