Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@ title: "Data Transformers"
url: /refguide/data-transformers/
weight: 50
description: "Describes Data Transformer documents in Mendix Studio Pro."
beta: true
---

## Introduction
Expand All @@ -12,10 +11,6 @@ Data Transformer documents transform data from one structure into another struct

You can use this feature to pre-process an incoming message (for example, from an API response or MQTT message) before an import mapping. You can also use it to transform a message before passing it on to a downstream system that expects the data in a specific structure.

{{% alert color="info" %}}
This feature is in beta.
{{% /alert %}}

### Prerequisites

* [Studio Pro 11.11](https://marketplace.mendix.com/link/studiopro/11.11.0) or higher
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@ title: "Data Transformer Use Cases"
url: /refguide/data-transformer-use-cases/
weight: 60
description: "Provides practical examples of common JSLT transformation patterns for Data Transformers."
beta: true
---

## Introduction
Expand All @@ -12,10 +11,6 @@ This document shows a variety of use cases that [Data Transformer documents](/re

Each walkthrough focuses on a specific use case you may encounter when working with real-world API responses, such as restructuring nested data, renaming fields, or combining metadata with data. Rather than covering every detail of the JSLT language, the walkthroughs are hands-on and immediately applicable. They show a concrete input, the expected output, and the transformation that connects the two.

{{% alert color="info" %}}
The [Data Transformer document](/refguide/data-transformers/) feature is in beta.
{{% /alert %}}

## Filtering Out Unused Fields {#filtering-out-unused-fields}

It is common for an API to return payloads that contain more fields than your app or a downstream system needs. Rather than passing the entire payload along, this transformation selects only the fields that are relevant, effectively dropping everything else. This keeps the output clean, reduces payload size, and avoids exposing unnecessary data.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.