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
AI-generatedOverview
This node interacts with the BEAS Service Layer API to retrieve a single 'Item' record by its ID. It is useful in scenarios where you need to fetch detailed information about a specific item from the BEAS system, such as inventory details or product specifications. For example, you can use this node to get an item's data by providing its unique ID, optionally selecting specific fields or expanding related entities for more comprehensive data.
Use Case Examples
- Retrieve an item by its ID to display its details in an inventory management system.
- Fetch specific fields of an item to optimize data usage in a reporting workflow.
- Expand related entities of an item to get associated data like supplier or category information.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the item record to retrieve. This is a required field for the 'Get' operation on the 'Item' resource. |
| Select | Comma-separated list of fields to include in the response. If left empty, all fields are returned. This helps to limit the data retrieved to only what is necessary. |
| Expand | Comma-separated list of related entities to expand in the response. If left empty, no related entities are expanded. This allows fetching related data along with the item. |
Output
JSON
json- The JSON object containing the retrieved item record data from the BEAS Service Layer API.
Dependencies
- BEAS Service Layer API endpoint URL and service password credentials for authentication.
Troubleshooting
- Ensure the provided item ID is correct and exists in the BEAS system to avoid 'record not found' errors.
- Verify that the BEAS Service Layer API credentials (URL and service password) are correctly configured and valid to prevent authentication failures.
- Check the JSON format of 'Select' and 'Expand' parameters to ensure they are comma-separated strings without syntax errors.
- If the node throws an error about session cookie retrieval, confirm that the BEAS Service Layer API is accessible and the login endpoint is functioning properly.