Review via Slack

Author: MariaShaposhnikova

content/en/docs/releasenotes/studio-pro/11/11.2.md

@@ -41,6 +41,7 @@ weight: 99
 - We fixed an issue where the **Back** and **Forward** navigation feature did not work with styling-related files. (Ticket 252248)
 - We fixed an issue that prevented updated workflows from being queued for execution when Mendix Runtime crashed during startup. (Ticket 253424)
 - We fixed an issue where some log nodes were not be available in the **Set Log Levels** dialog when running a Mendix app locally from Studio Pro. (Tickets 255330, 255510, 255776)
+- We fixed an issue in Import Mappings where object properties were not connected correctly to mapped attributes, resulting in empty import values. (Tickets 254351, 256716, 256726)
 - We fixed an issue where an enumeration with a value or a caption set to `com` resulted in a compilation error when you tried running the app. We have also added this to the [reserved words](/refguide/enumerations/#name) list. (Ticket 255976)
 - We added the refresh functionality for the Marketplace content when a session times out. The reload button will now close the details page and refresh the search tab view to ensure the latest information is displayed.
 - We resolved an issue where a view entity, when loaded without entity access, would throw an exception if it was used in a context requiring entity access.
@@ -49,7 +50,6 @@ weight: 99
 - We fixed an issue in offline synchronization (using the **Synchronize unsynchronized objects** and **Synchronize all** actions) that resulted in error log statements and **System.SynchronizationError** objects containing a text **Changing member failed for security reasons, no write access for changed member**. That was caused by the offline client trying to synchronize a change for a member that was inaccessible by that user.
 - We fixed an issue where two different error messages overlapped in the **Choose Branch line** pane after signing in and out.
 - We fixed an issue where Studo Pro crashed due to an XPath constraint being too long or complex to parse correctly. Now a consistency error message is shown instead.
-- We fixed an issue in **Import Mapping** document where values inside folded objects were not correctly parsed to a mapped attribute, resulting in empty values.
 - We fixed an issue that prevented line breaks from being added to the body editor of POST requests in Consumed REST Service documents.
 - We fixed an issue in external OData entity's object initialization where specifying the value for a key via a microflow expression failed.
 - We fixed an issue where the XPath aggregate function `sum` returned `0` for an empty result because the name was case-sensitive.