How to retrieve data which got wiped from a field during migration

Surendra Deshmu
Tera Contributor

‎08-08-2023 02:56 AM

Hello Team,

 

We're recently experiencing that we're not able to see values which we previously filled in glide list field.

 

we've checked and verified that there was no change as such done (column deletion, UI policy, BA or client script) which might've caused wiping out data from that field.

 

My first question was: what could possibly might be the reason for data removal from the field

 

Question 2: is there any way we can retrieve the previous data as it has not beed long since we're facing this issue and we might have something still in deleted records which I can restore and update the data.

 

One more thing: we can't see that glide list field on audit calender (since corresponding table is not audited we were checking on history calender to see if we can find something.)

 

Thanks 

Surendra

0 Helpfuls
  • 282 Views
1 REPLY 1

Ratnakar7
Mega Sage
Mega Sage

‎08-08-2023 05:24 AM

Hi @Surendra Deshmu ,

 

If data from a field got wiped out during migration and you're unable to determine the cause through regular configuration changes or logs, here are some steps you can take to investigate and potentially retrieve the lost data:

  1. Database Backups: Check if your organisation maintains database backups. If you have recent backups available from before the data was wiped out, you might be able to restore the database to a point where the data was intact.

  2. System Logs: Examine the system logs for any relevant entries around the time you noticed the reference field values being wiped out. Look for any error messages, warnings, or unusual activities that could be related to the issue.

  3. Business Rules and Workflows: Carefully review all business rules and workflows that could potentially affect that field. Even if you don't see direct evidence of changes in audit logs, it's possible that an automated process triggered the change.

  4. Script Includes and Scheduled Jobs: Check if there are any script includes or scheduled jobs that operate on the table or related tables. These scripts could be modifying the field values.

  5. Data Imports or Integrations: Investigate if there were any data imports, integrations, or data migration activities around the time the reference field values were cleared. Incorrect data mappings or integration logic could lead to unintended data changes.

 

Thanks,

Ratnakar

0 Helpfuls