Hi Kevin, I was finding a lot of duplicate attendees, and I found out that the provider of the update was creating some of those, by merging bad into the good. I was not aware until recently. Som...
See more...
Hi Kevin, I was finding a lot of duplicate attendees, and I found out that the provider of the update was creating some of those, by merging bad into the good. I was not aware until recently. Some of the data issues are the result of charges in their process, some are user errors. The list of winners, (keepers) and losers (duplicates and bad info) was provided by the number assigned to custom 25 field and also attendee name and custon 14. Many of the records do not have custom 25 populated, have duplicates in custom 14, or blanks and many people have the same name, or some were due to misspellings. All of the records have an external id. I had over 3800 merged ids, for 2020 alone, going 1 by one was not doable, and creating an import to deactivate required the ext. id. I wanted to make sure that when deactived I left ext id, name, custom 14 and 18 in the records. The best way to do that was creating a report to ensure that I was deactivating the same fields I was given. It also provided an opportunity to pull records with blank or duplicate custom 14, blank custom 25 (we use for sunshine reporting). And yet, I still found one today. The problem is I have 18k attendees that have been used in expense over the last 5 years, and have on multiple occassions added >50k records of HCPs at a time. So, what that tells me is that while I have been able to cleanse a few hundred that were in expense, I likely have many more in the config table that have been imported but I cannot see because they do not join to the used records, and I have not been able to pull a report to review, and if I do there is not external id. So that's why I used a report.