Skip to content

Conversation

@LEGIO-SEXTA-FERRATA
Copy link
Contributor

This PR adds the docs page for batch conversion for Mendix 10, making it the same as Mendix 11.
It can be merged for the next release.

@LEGIO-SEXTA-FERRATA LEGIO-SEXTA-FERRATA marked this pull request as draft January 19, 2026 09:24
@ConnorLand ConnorLand self-assigned this Jan 19, 2026
@ConnorLand
Copy link
Collaborator

@LEGIO-SEXTA-FERRATA Is this technology available to customers now? If so, we will edit and merge without waiting for a release.

@LEGIO-SEXTA-FERRATA
Copy link
Contributor Author

@LEGIO-SEXTA-FERRATA Is this technology available to customers now? If so, we will edit and merge without waiting for a release.

@ConnorLand hey 👋 , yes, we already released the feature for Mendix 10.24 LTS, so this is readily shippable. But we are doing our in-team review first, you can take over this PR after I undraft (which apparently is not an actual English word) it. 👍

@@ -0,0 +1,61 @@
---
title: "Batch Widget Conversions for React Client"
url: /refguide10/mendix-client/batch-conversion/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The release notes that announce the feature for 10.24.13 link to the current refguide, maybe we can update that link to refguide10?


## Introduction

When migrating your application to the [React client](/refguide/mendix-client/react/), you may need to convert multiple widgets that are not compatible with the React client. Studio Pro's batch conversion feature allows you to efficiently convert multiple unsupported widgets at once, rather than converting them individually.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When migrating your application to the [React client](/refguide/mendix-client/react/), you may need to convert multiple widgets that are not compatible with the React client. Studio Pro's batch conversion feature allows you to efficiently convert multiple unsupported widgets at once, rather than converting them individually.
When migrating your application to the [React client](/refguide10/mendix-client/react/), you may need to convert multiple widgets that are not compatible with the React client. Studio Pro's batch conversion feature allows you to efficiently convert multiple unsupported widgets at once, rather than converting them individually.


## Introduction

When migrating your application to the [React client](/refguide/mendix-client/react/), you may need to convert multiple widgets that are not compatible with the React client. Studio Pro's batch conversion feature allows you to efficiently convert multiple unsupported widgets at once, rather than converting them individually.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we want to use incompatible here instead of unsupported. Considering we support the conversion of some incompatible widgets, and we do not support the conversion of other widgets.

Suggested change
When migrating your application to the [React client](/refguide/mendix-client/react/), you may need to convert multiple widgets that are not compatible with the React client. Studio Pro's batch conversion feature allows you to efficiently convert multiple unsupported widgets at once, rather than converting them individually.
When migrating your application to the [React client](/refguide/mendix-client/react/), you may need to convert multiple widgets that are not compatible with the React client. Studio Pro's batch conversion feature allows you to efficiently convert multiple incompatible widgets at once, rather than converting them individually.

We may want to update this in the main doc as well.

The batch conversion feature automatically identifies all non-React widgets in your application which have an automatic conversion defined for React client compatibility and provides options to convert them in bulk. This significantly reduces the time and effort required to migrate large applications to the React client.

{{% alert color="info" %}}
Custom widgets and some platform-supported widgets cannot be converted automatically. You will need to review these and replace them with the equivalent React-compatible widgets.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Custom widgets and some platform-supported widgets cannot be converted automatically. You will need to review these and replace them with the equivalent React-compatible widgets.
Custom widgets and some platform-supported widgets cannot be converted automatically. You will need to review these and replace them with the equivalent React-compatible widgets manually.

Custom widgets and some platform-supported widgets cannot be converted automatically. You will need to review these and replace them with the equivalent React-compatible widgets.
{{% /alert %}}

The batch conversion feature was introduced in Mendix version 11.4.0.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually we have this information in a callout.

Suggested change
The batch conversion feature was introduced in Mendix version 11.4.0.
{{% alert color="info" %}}
The batch conversion feature was introduced in Mendix version [10.24.13](/releasenotes/studio-pro/10.24/#102413).
{{% /alert %}}

For refguide10 we may want to state 10.24.13 instead of 11.4.0


Click **Convert** to convert the selected widgets.

{{< figure src="/attachments/refguide/runtime/mendix-client/batch-conversion/batch-conversion-dialog.png" class="no-border" >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to keep a separate one for the refguide10 version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants