Actions17
- Auftrag(v1) Actions
- Adresse(v1/v2) Actions
- Rechnungsbeleg(v1) Actions
- Angebotsbeleg(v1) Actions
- Auftragsbeleg(v1) Actions
- Lieferschein(v1) Actions
- Gutschrift(v1) Actions
Auftragsbeleg(v1) → Alle abrufen
AI-generatedOverview
This node interacts with the Xentral ERP system, specifically to retrieve all records of the resource 'Auftragsbeleg(v1)' (order documents). It supports fetching multiple order documents with various filtering parameters such as page number, number of results per page, status, document number, customer number, date filters, project, sorting, and inclusion of sub-resources. This is useful for automating data retrieval from Xentral ERP for order documents, enabling integration with other systems or workflows that require order data.
Use Case Examples
- Retrieve all order documents with status 'angelegt' (created) for reporting purposes.
- Fetch order documents filtered by a specific customer number or date range for analysis.
- Include sub-resources like positions or protocol entries in the retrieved order documents for detailed processing.
Properties
| Name | Meaning |
|---|---|
| Datenbank wählen | Choose this option if using Xentral's multi-database feature to specify which database to query. |
| Datenbankname | Name of the database to query when multi-database option is enabled. |
| Abfrage Parameter | Collection of query parameters to filter the order documents retrieved. Includes pagination, filtering by status, document number, customer number, date ranges, project, sorting, and inclusion of sub-resources. |
Output
JSON
- ``
id- Unique identifier of the order document.belegnr- Document number of the order.status- Status of the order document.datum- Date of the order document.kundennummer- Customer number associated with the order.positionen- Included positions (line items) if requested.protokoll- Included protocol entries if requested.
Dependencies
- Xentral ERP API
Troubleshooting
- Ensure the API credentials for Xentral ERP are correctly configured and have sufficient permissions to access order documents.
- If using the multi-database option, verify the database name is correct and accessible.
- Check that query parameters are valid and within allowed ranges (e.g., page number and items per page not exceeding 1000).
- Common error: 'The operation is not known!' indicates an unsupported operation was selected; verify the operation parameter is set to 'Alle abrufen' for this resource.
- Common error: 'The resource is not known!' indicates an unsupported resource was selected; ensure the resource is set to 'Auftragsbeleg(v1)'.