Configure Your Accounts

Verify and Customize Your Account Model Settings

The Default Account Model setting determines which type of Account GEM creates for Contacts that don't have a related Account. Determine which Account Model best fits your org's business processes, and configure the Account Model settings.

With EDA installed, GEM automatically creates an Account for any Contact that doesn't have a related Account. The Default Account Model setting determines which type of Account GEM creates. (For more information, see Salesforce, Account Models, and the EDA Account Model.)

So which option should you choose for your default: Household or Administrative? Household Accounts are designed for tracking students as one of multiple Contacts belonging to the same family or household, a common choice for advancement offices. Administrative Accounts are designed as a container Account for a single Contact, commonly used for tracking a student primarily as an individual rather than a household member. We recommend you choose based on whether your users create more Contacts for prospective or actively enrolled students (Administrative), or for fundraising (Household).

1. Go to the EDA Settings tab.

2. Click the System tab.

3. Click Edit.

4. Verify the Default Account Model setting. Household is specified by default, but you can change it to Administrative if needed.

5. Select Automatic Household Naming.

6. Click Save.

If your Default Account Model is Household, also configure these settings.

1. In EDA Settings, click the Accounts and Contacts tab.

2. Click Edit.

3. For Account Types with Multi-Addresses Enabled, select Household Account.

4. For Account Types without Contacts to Delete, select Household Account.

5. Click Save.

Correct Existing EDA Account Data

Run a one-time script to clean your Account and Contact data for Single Gift Entry processing.

Account and Contact data must meet certain criteria to be used by Single Gift Entry, and if your org already had EDA installed, their data may not be fully compatible. Some of these fields aren't typically included in Account page layouts, so to make data cleanup easier, we’ve provided a script that does it for you. You need to run this script only once, during configuration.

1. Click , then click Developer Console.

2. From the Debug menu, click Open Execute Anonymous Window.

3. Copy this Apex code and paste it in the window.

   gem.Post_Install_Script.queueAccountProcessor();

4. Click Execute.