The Merge ID Utility is used to "clean up" your tables when you determine that you have two different ID Numbers for the same constituent. This utility will re-assign all of the data rows from one of the ID Numbers to the other ID Number.
The system will prompt you to identify a Merge From ID and a Merge To ID. This is done using a variation of the Search Abila Millennium Database form You may use the name, address, or ID number to identify constituents to the system as the Merge From and Merge To constituents (Advanced Searching is not available).
In this discussion, the Primary ID, or first constituent will be referred to as the Merge To ID constituent. The Secondary ID, or second, constituent will be referred to as the Merge From ID constituent.
This utility does not create a new copy of the information, but moves the information to the specified constituent. Once the data rows have been merged, they can only be accessed via the Merge To ID constituent's ID Number or Name.
This utility does not attempt to integrate the data from one row into another row, even if one of the same "type" is present. For example, if the Merge To ID constituent has an Address row with a Type of home, and the Merge From ID constituent also has such a row, following the merge, the Merge To ID constituent will own two rows with a Type of home. Since these may represent the same location, the information should be manually combined on to one data row and then the other row deleted. This should be done as part of the clean-up procedures following the run of the utility.
Each constituent may have either none or one row in the Death and the same applies to the Tracking table. If the Merge To ID constituent already has a row in these tables, the utility will not attempt to move another into it from the Merge From ID constituent. If the Merge To ID constituent does not own either a Death or Tracking row, the Merge From ID constituent's Death and/or Tracking row will be moved to the Merge To ID constituent.
For example, the Merge To ID constituent has a Death row and does not have a Tracking row. The Merge From ID constituent has both a Death row and a Tracking row. The system will leave the Merge From ID constituent's Death row in the Death table, under the Merge From ID constituent's ID number, but it will move the Merge From ID constituent's Tracking row to the Merge To ID constituent
The system will also leave the Merge From ID constituent's Basic Data row in the Basic Data table, under the Merge From ID constituent's ID number.
Comparing and then deleting the Merge From ID constituent's Tracking, Death and/or Basic Data rows should be done manually as part of the clean-up procedures following the run of the utility. However, the utility will offer the option, once the Merge is complete, to have the Merge From ID constituent's Basic Data, Tracking and/or Death rows removed automatically. Choose this option only if you are confident that you will not lose important information by doing so.
The Merge ID Utility does not move any Summary rows from one constituent to another. Summaries rows are not created using typical data entry procedures. They are only created by using the Summaries or Years Utilities. Since Summary data is calculated based on the Gift data table, Summaries must be re-created, via the Summaries or Years Utilities, for any Merge To ID constituent following the action of the Merge ID utility - particularly if Gift rows were moved from a Merge From ID constituent to a Merge To ID constituent.
Abila Millennium does not allow a constituent to have more than one spousal-type relationship. If the Merge To ID constituent has a spousal-type relationship and the Merge From ID constituent also has a spousal-type relationship, the utility will not begin the Merge process.
The utility will follow the same database 'rules' when creating the new data rows for the Merge To constituent as it would if the data was entered using standard data entry techniques.
This utility alters existing data on the system and is classified as a system administrator tool. Access to the utility is protected with a system password that has been provided to the system administrator at the time that Abila Millennium is installed.