Option to select fields that get updated when pulling in new applications (in new system)

In the previous application system, there was an option when downloading applications to select/deselect which fields were updated when the applications were pulled into the system.
In the new application system this function no longer exists. Additionally, it now updates the Organization record name, even if we don't want it to. For example, the record name (and legal name for the 501c3) is XYZ University Foundation. If the XYZ College of Education submits an application and types "XYZ College of Education" it changes the name on the record to XYZ College of Education. We do not want the Organization name updates to automatically happen.

  • Marissa Flynn
  • Mar 5 2025
Applications
  • Attach files
  • Amanda Phaneuf commented
    November 10, 2025 20:33

    I support this (and collectively on this issue you have way over 150 votes) - we should have basic control of what fields are overwritten, or at least parity with the legacy portal (the option to update or not update fields with new application data). The number of times an applicant misspells their org name, lists a different address, or lists their contact details slightly different (with a middle name or with an abbreviated name) is very high. Your solution of telling customers to 'create new' org and contact records instead of associating at consideration (to avoid the overwrite), then merging duplications at a high volume of 200 applications per day is (1) poor data integrity (2) incredibly risky and (3) needlessly and EXPONENTIALLY time consuming.

    Attachments Open full size
  • Anonymous commented
    July 11, 2025 17:46

    This is esential. IT should be an idea, it is literally how databases work.

    Attachments Open full size

Related ideas