New Allowed Table Session Event for Retention Policies#9683
Open
abaier5 wants to merge 1 commit into
Open
Conversation
Author
Contributor
|
Issue #9681 is not valid. Please make sure you link an issue that exists, is open and is approved. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Description
On the SQL side, this change was already implemented previously, but the BaseApp retention policy install codeunit does not yet include Session Event in its allowed table list.
To keep the AL side aligned with the existing SQL-side behavior, extend the retention policy initialization so that Session Event is added as an allowed table alongside the current system tables.
Expected Result
Retention policy installation in BaseApp adds Session Event to the allowed tables, matching the behavior already established on the SQL side.
Acceptance Criteria
Session Event is added to the BaseApp retention policy allowed tables.
The change follows the same intent as the existing SQL-side implementation.
Existing allowed tables remain unchanged.
Retention policy setup still completes successfully.
Related to #9681
Fixes #9681