Actions76
- Faktury Actions
- Příjemky Actions
- Prodejky Actions
- Objednávky Actions
- Výdejky Actions
- Pokladní doklady Actions
- Nabídky Actions
- Výroba Actions
- Interní doklady Actions
- Poptávky Actions
- Převod Actions
- Banka Actions
- Zakázky Actions
- Pohyby Actions
- Účetní deník (PÚ) Actions
- Adresy Actions
- Zásoby Actions
- Prodejní ceny Actions
Overview
This node integrates with the Stormware Pohoda accounting system, specifically enabling export operations for various data resources including contracts ("Zakázky"). The Export operation allows users to retrieve records from Pohoda based on filters and pagination parameters. It supports outputting data either as XML or parsed JSON objects.
Common scenarios include:
- Exporting contract records for reporting or synchronization with other systems.
- Retrieving filtered subsets of contracts by date range, ID, or other criteria.
- Exporting data in XML format for further processing or archival.
- Converting character encoding from Windows-1250 to UTF-8 for compatibility.
Example use case:
A user wants to export the latest 100 contract records starting from a specific record ID, optionally receiving the data as XML for integration with another system that requires XML input.
Properties
| Name | Meaning |
|---|---|
Return Records Count (count) |
Number of records to return in the export; valid range is 1 to 10,000. Default is 10. |
Start Record ID (idFrom) |
Minimum record ID from which to start exporting records. Optional filter to paginate or limit results. |
XML Output (xmlOutput) |
Boolean flag indicating whether to output raw XML data (true) or parsed JSON (false). Default is false. |
UTF8 Conversion (utfConvert) |
Boolean flag to convert response encoding from Windows-1250 to UTF-8. Default is true. |
Output
The node outputs an array of items corresponding to the exported records:
- If XML Output is enabled, each item contains a
jsonfield with a single propertydataholding the raw XML string response. - If XML Output is disabled, the node parses the XML response into JSON objects representing the exported records and outputs them under the
jsonfield. - In case of print operations (not relevant here), binary PDF data may be output, but for export, only JSON or XML text is returned.
Each output item is paired with its input item index for traceability.
Dependencies
- Requires an API authentication credential with access to the Pohoda system.
- Uses HTTP POST requests to Pohoda's XML API endpoint.
- Converts character encoding using the
iconv-litelibrary. - Parses XML responses using the
xmlbuilder2library. - Requires proper configuration of the base URL and credentials for Pohoda API access.
Troubleshooting
- Authentication errors: Ensure the API credentials (username and password) are correct and have sufficient permissions.
- Invalid filters or resource names: The node throws errors if unsupported resources or operations are requested.
- Encoding issues: If the output contains garbled characters, verify the UTF8 Conversion setting; disabling it will return raw Windows-1250 encoded data.
- API errors: The node surfaces error messages returned by Pohoda in the
NodeApiError. Check the message for details such as invalid request parameters or server-side issues. - Large exports: When requesting many records, ensure the count does not exceed 10,000 and consider paginating using the Start Record ID.