CONTACT USBack to MinistryPlatform Site
Your Knowledge Base has moved to the new Help Center.  Check out the release notes for details. And don't forget to update your bookmarks and in-house documentation before May 28.

Data Quality Routine

 

This nightly routine performs various clean-up tasks in the database including:

People Records

Contact Syncing

The routine syncs Contacts with Donors/Participants/Users. See Routines FAQ for more information on how the SVC MNGR syncs these records.

  • Contacts.Donor_Record with Donors.Donor_ID
  • Contacts.Participant_Record with Participants.Participant_ID
  • Contacts.User_Account with dp_Users.User_ID
Other Contact Cleanup
  • Adds Suffix to display name on any Contact that has one.
  • Assigns household position of "Company" to any contact record where Contacts.Company = 1 (yes/true).
  • Changes all email addresses to be lower case.
  • Populates missing Nickname values. If the Nickname field is null, the routine will auto-populate the Nickname field with the First Name.
  • Adds a title on the Care Case page when a Care Case is created. It shows the Care Type and Display Name of the Contact (when there is one) or the Household (when there is not a Contact).
  • Updates the Participant End Date field when it is null and the Contact's status is Inactive or Deceased.
  • Clears the Participant End Date field if it is populated and the Contact's status is not Inactive or Deceased.

Stewardship

  • Deletes any unused Donor Account records assigned to the Default Contact.
  • Merges any duplicate Donor Account records for a Donor based on matches for a value greater than five in that field.
  • Donation Distributions will be credited to active Pledges that were, for whatever reason, not credited. Pledges will be credited if all of the following are met:
    • The Donation is distributed to a Program that is connected to a Pledge Campaign to which the Donor or spouse has an active Pledge. 
    • Donation Distribution Pledge is null.
    • The Donation date is later than the First Installment date of the Pledge.
    • The Donation date is within the last 90 days.
    • AssignPledgesNightly configuration setting is set to Yes.
  • Updates corresponding Spouse when one Spouse's Statement Type, Method, or Frequency is updated. Note: To enable this update, you must set at least one of the following Configuration Settings to "true"; (pick and choose the ones that work for your church!):
    • SSRS, SyncSpouseDonorType - Updates corresponding Spouse's Statement Type.
    • SSRS, SyncSpouseDonorMethod - Updates the corresponding Spouse's Donor Method.
    • SSRS, SyncSpouseDonorFrequency - Updates the corresponding Spouse's Statement Frequency.
  • Pledge totals are increased to match donation totals. Any changes made by this routine are recorded as pledge adjustments with an adjustment type of Auto Increase. By default, the total will match the sum of all donation distributions assigned to the pledge in the last 90 days. You can change this date range if needed, but note that increasing the number of days may affect performance.
    • SSRS, AssignIncrementPledgeDays - Controls the date range of donation distributions assigned to the pledge.

Groups and Participation

Group Is Full
  • Sets Groups.[Group_Is_Full] to true when the count of Group Participants is greater than or equal to the Target Size of the Group.
    • If the COUNTGROUPINQUIRIES Configuration Setting is true, the count is based on the combination of Inquiries where Placed = null and Group Participants of the Group compared to the Target Size.
    • If Group_Is_Full = true already, the routine will not set back to false. This can be done manually, if desired, at the timing and discretion of the church.
  • Note: This routine runs every 15 minutes.
Group Participants
  • Merges duplicate Age or Grade Group Participant records where one Participant has more than one record in the same Group or with the same role.

Forms and Invoices

  • Anyone associated with a Form Response record that came from the Opportunity Finder will be updated with the same person once the Response record is updated. 
  • The Recipient associated with an Invoice Detail record that came from Event Registration will be updated with the same person once the Event Participant record is updated.

Attendance

  • Updates Last Attendance Date on Participant record as appropriate from recent attendance posted (the attendance could be for a past, current or future event - the routine looks for the most recent 03 Attended or 04 Confirmed status).
  • End dates any current Group Participants on Groups where the End Date was added at the Groups creation (before the Group Participants were added to the Group).
  • Updates Last Attendance Posted and Last Group Member Change fields on the Group record.

Groups and Events

  • Creates Event_Groups for any Groups found in Event_Rooms table that are associated with future Events. This way, reports and tools that are leveraging Event_Groups will still be valuable during the transition to using Event_Rooms as part of the new Check-In Suite. Note: The Routine will only add Event Groups for Events with a Start Date more than 30 days in the past.
  • Sets Event_Rooms.__Primary_Reservation (hidden field on Groups & Rooms sub-page) to allow views and reports to target this field to get back only the most relevant record associating a room with an Event when a Room is associated multiple times with an Event in order to accommodate multiple Groups sharing a Room as is common in some Check-In Suite scenarios.

Register Into Series

Anyone who is registered for a future Event in a series will automatically be added to all future Events in the series. See Register Into Series.

Administration

  • Replaces "WebUser" with the actual user name in the audit log when possible.
  • Removes In Recovery from user accounts. After a specified time the temporary password issued will expire and the user will need to begin the process again.
  • Removes any empty "Current/Unsaved Selections".
  • Reviews Configuration Settings for instances when a primary key integer value that is being used as a configuration setting is no longer present in the table. An alert about this situation will allow a technician to update the value to a value that does exist. This will prevent application errors.