From 7087c6051beb1d1f5da41107b2f833d8477ebd26 Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Mon, 27 Oct 2025 10:47:16 +0100 Subject: [PATCH] Add a known issue note for the view entity context switch issue still present in 10.24 --- content/en/docs/releasenotes/studio-pro/10/10.22.md | 1 + content/en/docs/releasenotes/studio-pro/11/11.0.md | 2 ++ content/en/docs/releasenotes/studio-pro/11/11.2.md | 2 +- 3 files changed, 4 insertions(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/studio-pro/10/10.22.md b/content/en/docs/releasenotes/studio-pro/10/10.22.md index d7a8f4fa4bd..92d588dbbc8 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.22.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.22.md @@ -122,3 +122,4 @@ weight: 78 * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-runtime-only) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-runtime-only). * In the React client, the debugger does not reconnect when restarting an app. * Fixed in [10.24.4](/releasenotes/studio-pro/10.24/#fix-debugger-reconnect) and [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect). +* When loading a view entity without entity access applied, an exception is thrown if it is then used in a context requiring entity access. (Tickets 257900, 259602, 260557) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.0.md b/content/en/docs/releasenotes/studio-pro/11/11.0.md index 1735b21b391..4000e604d55 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.0.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.0.md @@ -360,3 +360,5 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-runtime-only). * In the React client, the debugger does not reconnect when restarting an app. * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect). +* When loading a view entity without entity access applied, an exception is thrown if it is then used in a context requiring entity access. (Tickets 257900, 259602, 260557) + * Fixed in [11.2.0](/releasenotes/studio-pro/11.2/#fix-view-entity-context-switch). \ No newline at end of file diff --git a/content/en/docs/releasenotes/studio-pro/11/11.2.md b/content/en/docs/releasenotes/studio-pro/11/11.2.md index 7a241e593b2..8d568885de0 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.2.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.2.md @@ -45,7 +45,7 @@ weight: 98 * 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. +* 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. * We fixed an issue where an OQL GET request with something that was not a `SELECT` returned results instead of throwing an error. * We fixed an issue in OQL where declaring an alias for a table in an outer query and using that alias in a union in a subquery resulted in an exception that the alias could not be found. * 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.