Skip to content

Add a known issue note for the view entity context switch issue #10276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 30, 2025
Merged

Add a known issue note for the view entity context switch issue #10276

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions content/en/docs/releasenotes/studio-pro/10/10.22.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 2 additions & 0 deletions content/en/docs/releasenotes/studio-pro/11/11.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
2 changes: 1 addition & 1 deletion content/en/docs/releasenotes/studio-pro/11/11.2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
* <a id="fix-view-entity-context-switch"></a>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.
Expand Down