PlantScanner - BEAS Service Layer icon

PlantScanner - BEAS Service Layer

Interact with BEAS Service Layer API

Actions32

Work Order BOM → Get All

AI-generated

Overview

This node interacts with the BEAS Service Layer API to retrieve all records of the Work Order BOM (Bill of Materials) resource. It supports filtering, sorting, pagination, field selection, and expansion of related entities, making it useful for scenarios where users need to query detailed BOM data from BEAS for reporting, integration, or automation purposes.

Use Case Examples

  1. Retrieve all Work Order BOM records created after a specific date using an OData filter.
  2. Get the top 10 Work Order BOM records sorted by creation date in descending order.
  3. Fetch Work Order BOM records including related WorkOrderLines and WorkOrderComponents entities.

Properties

Name Meaning
Filters OData filter string to filter the Work Order BOM records (e.g., Status eq 'Open' or CreationDate ge '2024-03-20').
Sort OData sort string to order the Work Order BOM records (e.g., CreationDate desc or Status asc).
Skip Number of records to skip for pagination purposes.
Top Maximum number of Work Order BOM 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 retrieved Work Order BOM records and their data.

Dependencies

  • BEAS Service Layer API
  • API authentication via service password to obtain session cookie

Troubleshooting

  • Ensure the BEAS Service Layer API URL and service password credentials are correctly configured.
  • Verify the OData filter and sort strings are valid according to BEAS API specifications.
  • If the session cookie is not obtained, check the service password and API endpoint accessibility.
  • Handle JSON parsing errors in input parameters for select and expand fields.
  • Common error messages include authentication failures, invalid OData queries, and network connectivity issues.

Discussion