feat: data remediation / conversion - #231
Merged
Merged
Conversation
plakkara-bc
approved these changes
May 1, 2026
mdiapenabc
force-pushed
the
feat/data-remediation
branch
from
May 1, 2026 20:25
025ab2a to
8138608
Compare
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
2 participants
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.
Description
Add one-time CSA status remediation script
Adds scripts/remediation/csa-status-remediation.sql, a manually executed SQL script to correct csa_status and din values on approximately 1000 contacts that have incorrect data in the CSA application.
The script follows a 5-step process: duplicate check, pre-check, UPDATE inside a transaction, post-check, and a prompt to trigger the existing SYNC_ICM job to push the corrected values back to ICM.
The VALUES block is populated from the MIS extract CSV (stored on SharePoint) using a spreadsheet formula before execution. The script is intended to be run by an authorised operator directly against the database — first on Pre-Prod to validate, then on Production.
No application code changes are included.