Expand DIT data overwrite logic
The customer would like to expand the logic of how the DIT overwrites data being imported to be more than just going by the most recent date in the "DateUpdated" field: "We have several systems that do not collect Race/Ethnicity/Veteran status, and we would hate to overwrite thousands of good quality race/eth/vet records to NULL.... It has been a challenge having to clean it up with each new dump. And cleanup is necessary because these are HUD fields and affect HUD reporting..." Perhaps make the data overwrite process more customizable?
Thank you for your feedback. We are currently reviewing this request.