Skip to main content

User Transformations

Tools – Custom Transformations

Written by Zuzana Sýkorová

🔄 User Transformations

Location in the application:
Nástroje → Uživatelské transformace

🧩 What are user transformations

User XSLT transformations allow you to easily:

  • create custom data transformations

  • manage them directly within the system

  • reuse them repeatedly (e.g. via API)

Unlike built-in transformations:

  • they are stored as regular user records

  • no request for implementation into ABRA Flexi is required

💡 Tip
User transformations are ideal for quickly adjusting outputs (XML/JSON) without modifying the system or requiring development on the ABRA Flexi side.

⚠️ Note
Creating transformations requires knowledge of XSL (XSLT). Without this knowledge, transformations cannot be correctly created or edited.


🗂 User transformation records

The list of transformations is available in the agenda:

Tools → User Transformations

Click the New button to open the form for creating a new record.

Code: A unique transformation identifier. Used when calling the transformation (e.g. in the REST API).

Name: The name of the user transformation for clear record-keeping.

Query: Contains the complete transformation definition written in XSLT.

💡 Tip
It is recommended to use consistent code naming conventions, for example based on the document type or transformation purpose (e.g. faktura_export, isdoc_uprava).

__________________________________________________________________

⚙️ Using user transformations

User transformations work the same way as built-in transformations.

They are primarily used in the REST API for:

  • modifying retrieved data (GET)

  • modifying data being saved (POST/PUT)

🔗 Usage in the API

To apply a transformation, use the following parameter:

?format=code:{zkratka}

where {zkratka} is the transformation code defined in the records.

📌 Example

Applying a transformation with the code yxz:

/c/demo/faktura-vydana.xml?format=code:yxz

This applies the user XSLT transformation to the invoice data.

⚠️ Note
If the specified code does not exist or contains an error, the transformation will not be applied and the API will return the standard output or an error.


❓ Frequently Asked Questions (FAQ)

  1. What happens if I specify a non-existent transformation in the API?

    The transformation will not be applied and the API will return the standard output or an error.

  2. What are transformations most commonly used for?

    Typically for:

    • integrations with external systems

    • modifying XML outputs

    • converting data structures

Did this answer your question?