10.8.1

Stable

March 08, 2024

Mendix Studio Pro is our low-code IDE for professional developers. It's a powerful visual model-driven development environment to build apps on the Mendix Platform. With Studio Pro you can easily create, change, integrate, test and deploy your applications, all in one place. Moreover, you can manage branch lines and security as well as extend your app with custom code using the built-in editors. Click 'Download Studio Pro' to get the installer for free (Windows OS required*). Learn more about the installation and the Studio Pro capabilities in our documentation. Not a professional developer? Learn How Mendix supports different developer profiles .Before installing, please read the Release Notes to learn about improvements, bug fixes, backwards compatibility, breaking changes and known issues. *If you are using a Mac, check out these instructions first.

Release Notes - **Release date: March 8, 2024** ## Fixes * We fixed an issue where renaming an attribute or its data type was not possible if you had any columns unselected in the data preview. ### Known Issues * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](https://docs.mendix.com/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](https://docs.mendix.com/refguide/version-control-menu/#show-changes) dialog box. * Workaround: For details, see [this section](https://docs.mendix.com/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*. * For some activities in the logic editors, the types of variables are not visible or shown as **Not set**. This is only a visual bug. (Tickets 205751, 207251) * In some cases, even if you are already logged in to Studio Pro, you might still need to click **Sign in** under the **MendixChat** tab to make MendixChat available for use. * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions. * On macOS it is not possible to exclude documents, and in the **App Explorer** not all context actions on selections work properly. * When the `com.mendix.storage.azure.BlobEndpoint` runtime setting contains the container name as a suffix (for example, https://account.blob.core.windows.net/example-container/), files stored in Azure will be stored at the top-level without a directory hierarchy. Previously they would have been stored in a directory hierarchy which means that the app can no longer access previously-stored files. (Ticket 210679)