Skip to content

Update side-effects-breaking-changes.md #140

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update side-effects-breaking-changes.md #140

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
2 changes: 1 addition & 1 deletion src/release-articles/11/side-effects-breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ As such, before introducing a breaking change for a new release, OutSystems care

**Rationale**: During a solution publish, Logical Database configurations were fetched by ExtensionID at a deployment stage where that value could be `NULL`, causing configurations to not be set correctly.

**Fix**: Updated the `Async_Operation_LogicalDatabase` entity to include the SS_Key attribute, and updated the solution publish process to use it to fetch the Logical Database configuration. It is advised that customers who have referenced `Async_Operation_LogicalDatabase` in a module must refresh their module's dependency on the ServiceCenter module.
**Fix**: Updated the `Async_Operation_LogicalDatabase` entity to include the SS_Key attribute, and updated the solution publish process to use it to fetch the Logical Database configuration. It is advised that customers who have referenced `Async_Operation_LogicalDatabase` in a module must refresh their module's dependency on the (System) module.

### Introduced in Platform Server 11.33.0

Expand Down