Jira Ticket: ECSTAKE2-12
Priority: Medium
Components: None
Description
Description: Miami Waterkeeper (ID 4003) previously uploaded a file, “windfall-edited-miami-waterkeeper.csv,” where the same constituents had different IDs. For example, Peggy Ochandarena appears in the file with several different NationBuilder IDs (62022, 64233, 66477, etc.) tied to separate donations. I did not notice this issue during validation; I only noticed this issue while verifying the enriched output. Fortunately, they hadn’t accessed or downloaded the file yet.
Actions already taken:
- Immediately ignored the problematic file in the portal so it is no longer downloadable
- Requested a corrected replacement file from the customer
- Customer has now uploaded a new file
- Scheduled meeting for re-training session on uploading data on 3/17/2026
Eng Request: Can we purge this account so I can map & match the new file?
Triage Comments
Triage Review — CRM Write Issues Pass
🟡 Priority: Medium — Confirmed correct. Miami Waterkeeper (4003) had a problematic file with duplicate constituent IDs that was caught before the customer downloaded it (good catch). The file has been ignored in the portal and a corrected replacement has been uploaded. Engineering needs to purge the account data so the new file can be mapped and matched. No customer data exposure occurred.
Jira Ticket: ECSTAKE2-12
Priority: Medium
Components: None
Description
Description: Miami Waterkeeper (ID 4003) previously uploaded a file, “windfall-edited-miami-waterkeeper.csv,” where the same constituents had different IDs. For example, Peggy Ochandarena appears in the file with several different NationBuilder IDs (62022, 64233, 66477, etc.) tied to separate donations. I did not notice this issue during validation; I only noticed this issue while verifying the enriched output. Fortunately, they hadn’t accessed or downloaded the file yet.
Actions already taken:
Eng Request: Can we purge this account so I can map & match the new file?
Triage Comments
Triage Review — CRM Write Issues Pass
🟡 Priority: Medium — Confirmed correct. Miami Waterkeeper (4003) had a problematic file with duplicate constituent IDs that was caught before the customer downloaded it (good catch). The file has been ignored in the portal and a corrected replacement has been uploaded. Engineering needs to purge the account data so the new file can be mapped and matched. No customer data exposure occurred.