[Main]Cannot Rename User Due to Financial Report Audit Log Permissions - Copy - #10991
Conversation
Good Sense Reviewer - Round 1Recommendation: AcceptWhat this PR doesThis change adds Financial Report Audit Log to the user rename permission list and to the existing BaseApp-specific rename handler in both W1 and RU. The event publisher was verified in the User codeunit. It runs before the generic rename path, and this table's Problem-solution fitFit: Strong The reported scenario is clear: audit log rows with the old user name must not block a later user rename. The diff targets that exact table and uses the same established handler used for other User-related BaseApp tables. SuggestionsNone. Risk assessment and necessityRisk: Low. The change adds one table to existing user rename handling and adds matching indirect permissions in both W1 and RU. The existing generic user-rename test should exercise this relation table, and the relevant build and test checks are green. Necessity: Necessary. Without this change, a user with Financial Report Audit Log rows can fail user rename or leave rows under the old user name. The scope is tight and matches the missing table.
|
Bug 648875: [Master][All-e][FTE][SaaS] Cannot Rename User Due to Financial Report Audit Log Permissions - Copy
Fixes AB#648875
Issue:
When a user was renamed, existing Financial Report Audit Log entries continued to reference the old user name.
Cause:
The Financial Report Audit Log table was missing from the Base Application’s user-renaming logic and required permissions.
Solution:
Added the table to the user-renaming handler and granted the required modify/rename permissions. Added a test verifying that audit-log entries are updated with the new user name.