Agile ConnectLink™ Installation

Step-by-Step Instructions

Version 4.6 Installation

Thank you for choosing Agile’s ConnectLink™ SalesForce integration application. These instructions should encompass everything you need to get started, but if questions arise at any time, please contact your Agile Account Manager for additional support.

  1. Because contacts in schools or districts often have multiple roles and can be assigned to multiple buildings; Agile has chosen to utilize the standard “Related Account/Contacts Object” to avoid the creation of duplicate contacts. Before installation, this package requires that the “Allow users to relate a contact to multiple account” setting to be enabled – which is off by default. If it’s already enabled, you can skip to Step 2 below.
    • To Enable the Related Account/Contact object you need to go to the “Account Settings” in the setup menu. See the screenshot to the right:
  • Note that enabling this setting may take a while. A related list for both contacts and account will be enabled and for any contact related to an account a related contact record will be created. These records are required by the app as they do not take any additional storage space and allow educators (contacts) to be related to as many schools (account) as necessary.
  1. The latest version 4.6 of the ConnectLink™ Application can be downloaded by clicking on the link below or through the App Exchange. Please install for all users. https://login.salesforce.com/packaging/installPackage.apexp?p0=04t5d000000ghW6&isdtp=p1

To install in a Sandbox environment, use this link: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5d000000ghW6&isdtp=p

  1. Once the app is downloaded, you will need to complete the ConnectLink Setup to access your licensed data from the Agile database through ConnectLink. With these installation instructions, you received both your Client ID and Client Key from your Agile Account Manager.
  1. In ConnectLink Setup, add your credentials (the Client ID and Client Key). ConnectLink setup, adding Client ID and Client Key (see image to the right).
  1. During the installation process, several fields were added to your Salesforce subscription as custom fields.
    • The added account fields include:
      1. Created by ConnectLink
      2. ConnectLink Key
      3. ConnectLink Last Sync Date
      4. ConnectLink Parent Key
      5. ConnectLink Parent Pending
      6. ConnectLink Status
      7. ConnectLink Do Not Update
    • The added contact fields include:
      1. Created by ConnectLink
      2. ConnectLink Key
      3. ConnectLink Last Sync Date
      4. ConnectLink Status
      5. ConnectLink Do Not Update
  1. Next in ConnectLink Setup, click “Update License Data” to retrieve the fields associated with your data license. You will also need to click “Update License Data” anytime that changes are made to your data license.
    • The added lead fields include:
      1. Created by ConnectLink
      2. ConnectLink Key
      3. ConnectLink Last Sync Date
      4. ConnectLink Status
      5. ConnectLink Do Not Update
    • The added related account/contact fields include:
      1. Compound Key Ext
      2. Compound Key Formula
      3. ConnectLink Inactive Roles
      4. ConnectLink Roles

You’ll need to add the ConnectLink Key, Parent Key, and ConnectLink Status fields to your account layout in Salesforce to support the ConnectLink integration. The ConnectLink Key and ConnectLink Status needs to be added to the contact layout as well. Lastly, the ConnectLink Sync, ConnectLink Matching, and Report CL Data Problem custom buttons should be added to both the account layout as well as the contact layout.

  1. Add Related Contacts to the Account layout to see the positions that the contacts associated with the Account have, you need to add the related list to your layout and add the ConnectLink Roles/ConnectLink Inactive Roles fields to the list.
  1. Repeat this process, adding Related Account to the contact layout (see image at right).
 
  1. You will need to ensure your license for Salesforce allows for the amount of data licensed from Agile. Use this formula as a guideline on how much storage is required.

A = Number of Account

C = Number of Contacts

O = Number of Objects

A + C = O

O x 2 KB = Number of KB needed to accommodate the new data

Example: 10,000 Account; 25,000 Contacts

10,000 + 25,000 = 35,000 Objects

35,000 x 2 KB = 70,000 KB

70 MB Required

The application will only import a portion of the additional data if there is insufficient storage available.
  1. You can now load the data returned to you from the Agile match into Salesforce. All you need to do is load the ConnectLink Key into your existing Account and Contacts, using your Salesforce ID as your identifier.
  2. This is also a good time to import the file of missing institutions provided to you. These are institutions that you lease, but do not currently exist in your Salesforce org. The Inst_UID in the file needs to be mapped to the ConnectLink Key in Salesforce.
  3. Any account and contacts that are added to your Salesforce environment through ConnectLink are flagged as an Agile record by checking the Created by ConnectLink box. This helps you comply with the Agile purge requirements at the end of the contract term if you choose not to continue with your data license. Please refer to your contract terms and conditions for more information.
  4. Review the data fields you have received from Agile and add any custom fields to your Salesforce layout that you’d like to have displayed. Ensure that you are using the correct data type for the field, otherwise the application will produce an error. Use the Agile Data Dictionary to match the Agile data type with the Salesforce data type.
  1. At this point, you’ll need to perform the field mappings in the ConnectLink Setup. When the preference is set to “Agile Ed” or “Choose Agile Ed” the Agile data is preferred over the current information in Salesforce. For individual account or contact updates, the “Choose” option allows the individual user to select from the two options and determine whether to overwrite the existing Salesforce data with the Agile data. For bulk updates the “Choose” option is ignored. For “Salesforce” and “Choose Salesforce” the Agile data is used only to fill empty fields. The “Choose” option is only available for single record updates.
  1. After you have mapped all fields, you are now able to update your Salesforce CRM from Agile’s database by clicking on the “ConnectLink Sync” button for individual account. Update an individual account in Salesforce using the ConnectLink Sync button to ensure that your mapped fields display properly, and the update occurs without error.
  1. Once you have verified that the individual update has completed successfully, you can click the New Institutions tab on the top of the page to load in licensed institutions that are not currently in your Salesforce. You can also use this function later to find institutions that have been newly added to the Agile database or use the Search tab to look up single institutions to add to your Salesforce.
  1. In the case that you have an existing account or contact without a ConnectLink key, you can use the ConnectLink Account Matching/ConnectLink Contact Matching buttons. For the account matching to function there needs to be a name and a state – either in the standard Billing or Shipping address fields.
    • If an account has a ConnectLink key already and you use the matching button/action the school that matches the key will not be shown – a suggestion that the user use the “Sync” function will be displayed as that will pull the newest data as shown below.

ConnectLink Version 4.6 Release Notes

Agile is available to help walk you through these steps and answer any questions that ar

With version 4.6 of ConnectLink we are introducing several new features that have been requested by our users.

  • A new button to allow clients to report data issues directly and easily.
  • The ability to edit existing field mappings, without having to delete and then re-add them.
  • The ability to sort existing mappings.
  • Newly mapped fields are displayed at the bottom of the Object’s field list.
  • The bulk update now has a confirmation message before starting.
  • We’ve added the ability to “roll-up” school level staff to the district level for those companies that market at the district and not the school level.
  • The “match on email address” feature matches contacts and leads on email address.
  • There has been additional work “under the hood” to make ConnectLink even more robust.

Lead Object

There is a section for mapping the Lead Fields.

This section is used to map any of the fields in the lead object that you’d like to update from your Agile data license. You’ll notice that these fields contain information on both the individual as well as the institution. It’s important to populate both so that when a Lead is converted to an Account/Contact the fields can carry over to aid further contact with the school or individual.

This section is used to map any of the fields in the lead object that you’d like to update from your Agile data license. You’ll notice that these fields contain information on both the individual as well as the institution. It’s important to populate both so that when a Lead is converted to an Account/Contact the fields can carry over to aid further contact with the school or individual.

There are also options on the “Actions” menu allowing the administrator to determine if new educators are to be inserted as Contacts or Leads. If you select “Import New Educators as Leads” then any prospects that are not related to an existing account will be added as leads. New educators that are related to existing Account will continue to be added as new Contacts for those Account.

  • Once you have converted a lead, you’ll need to click on the ConnectLink Account Matching button so that you can Sync this new account with the Agile database.

 

 

 

 

 

  • Select the correct school or district and click Sync/Merge to assign the ConnectLink Key and update the information.
  • The ConnectLink key will be assigned, and the account will be synced and all the contacts will be loaded for that account.

Scheduling Bulk Updates

  • Click Apex Classes from the Salesforce Setup.

 

  • Click Schedule Apex
  • Click Apex Classes from the Salesforce Setup.

 

  • Click Schedule Apex
  • From Apex Class, select BatchUpdateObjects.

Do Not Update Flag

  • There is a field called “ConnectLink Do Not Update” – when it is checked it should keep that record from being updated by batch processes.

 

 

 

 

 

  • The processes that ignore Contacts/Account that have this field set to true are the Account Hierarchy batch, the Bulk Update/Bulk Update All, account when Sync Entire District (from the sync modal) is selected and contacts when “Sync Personnel” is selected from the account sync page.

 

  • The ConnectLink Status will update even if the Do Not Update box is checked.

Matching of Accounts and Contacts

  • There are two-page buttons/Lightning actions for account and contacts–ConnectLink Account Matching/ConnectLink Contact Matching. For the account matching to function there needs to be a name and a state–either in the standard Billing or Shipping address fields.
  • If an account has a ConnectLink key already and you use the matching button/action the school that matches the key will not be shown – a suggestion that the user use the “Sync” function will be displayed as that will pull the newest data as shown below.

When the user clicks “Sync/Merge” with a record that already exists in the SF database 2 things happen.

  • The record that matches (the “existing” record) will be synced with the data from agile according to the mappings. 
    • Any fields that are blank on the existing record that are not blank on the viewed record will be populated with the viewed record data. But the “existing” record is the master and will not have any data overwritten.
    • Any cases/opportunities/contacts will be migrated to the “existing” account and the viewed account will be deleted. There is a warning/confirm dialog will be displayed to the user before anything is committed.

If there is a record that is matched in the database that is not part of the subscription of the client a message will display informing the user that it is not part of their subscription and only minimal data will be applied (the key will be added, name updated and in some cases address information).

Glossary

Update License Data
Bring in all licensed fields to be used for mapping.

Bulk Update
Update all accounts and contacts that have been updated on Agile’s database since the last bulk update.

Bulk Update All
Update all accounts and contacts regardless of when they were last updated.

Turn Off Automatic (account hierarchy)
Disables automatic re-parenting of existing accounts based on Agile’s data.

Re-Parent All
Re-parents accounts per Agile’s standard hierarchy, this is also performed during Bulk Update All

Turn Off Automatic (contact hierarchy)
Relates the contact to the correct account(s) when performing updates.

Block New Educators
This determines whether new contacts are imported with updates or if only existing contacts get updated.

Allow New Educators
Enables/Disables the creation of Contacts or Leads depending on the other configuration choices.

Enable/Disable Leads
Enables the sync(s) to update leads as well as allow for new educator records to be created as leads.

Bulk Match Lead Emails
Goes over all existing leads that do not have agile keys and attempts to set a key to them via an exact match on email.

Import Missing Leads
Batch job that imports leads that do not belong to any accounts that are currently in the system (will not create accounts, will create leads with no account attached).

Import New Educators as Leads
Toggle to have the app import educators either as Leads or Contacts.

Clean Mappings (field mappings)
Removes any unlicensed fields from mapped fields.

Possible Duplicates
During the match process, multiple records may match to the same account, contact, or lead. They are considered possible duplicates because we base these results off fuzzy matching algorithms and may include records that are intentional duplicates.

New Institutions
Tab that allows bulk import of institutions that have been added to the Agile database since the last date the import was run.

Search tab
Tab that allows a single institution import based on user search.

Report CL Data Problem
Button that allows the user to report a data problem directly to our data compilation team.

ConnectLink Account Matching
Button that allows a user to match an account to the AgileEd database and append a ConnectLink Key to the record.

ConnectLink Contact Matching
Button that allows a user to match a contact to the AgileEd database and append a ConnectLink Key to the record.

FAQ

How can you re-order the selection screen that pops up when you click ConnectLink Sync button?
You cannot change the order of these fields; they show up in alphabetical order.

Is there a way to edit a current mapping?
Delete and start over is currently the only option available.

How can I assign a ConnectLink Key to a record that doesn’t have one?
You can use the ConnectLink Account/Contact/Lead matching button to import a ConnectLink Key.

How do we add new accounts from Agile into SFDC?
You can use the New Institutions tab or the Search tab to import new accounts.

Can we add educators in as Leads?
Yes, ConnectLink has the option to integrate with the lead object.

What is the difference between Bulk Update and Bulk Update All?
Bulk Update All updates all Institutions and Personnel that are part of the licensed data set. Bulk Update will update accounts and contacts that have been updated on Agile’s database since the last bulk update.

How long does it take for the update to complete, is there a progress indicator? How will we know when the job is completed?
The update will probably take 6-24 hours in total, depending on the speed of the writes into Salesforce and other factors. The update process will spawn a series of Apex Jobs and you can see the progress of the individual batches. You will receive an email once the update is complete.

Should I install the package for all users?
Yes!

How do we restrict permissions?
You can hide either the tabs or the entire app based on profile.

What does the Prefer menu mean?
When the preference is set to “Agile Ed” or “Choose Agile Ed” the Agile data is preferred over the current information in Salesforce. For individual account or contact updates, the “Choose” option allows the individual user to select from the two options and determine whether to overwrite the existing Salesforce data with the Agile data. For bulk updates the “Choose” option is ignored. For “Salesforce” and “Choose Salesforce” the Agile data is used only to fill empty fields. The “Choose” option is only available for single record updates.

How do I grant login access?
See step by step instructions here: https://help.salesforce.com/articleView?id=granting_login_access.htm&type=5

Can more than one account, contact or lead have the same ConnectLink Key?
No, the ConnectLink Key is a unique identifier and may not be assigned to more than one account, contact
or lead.

Can a lead and a contact have the same ConnectLink Key?
Yes, a single ConnectLink Key can be assigned to a lead and a contact.

Duplicate accounts/contacts not updating?
Duplicate accounts and contacts may not update if you have duplicate rules turned on and set to notify when created or updated. This can be resolved by either turning off the duplicate detection rule prior to running updates or by adjusting the settings to only alert upon creation. If this occurs, either Account Name:DUPLICATES_DETECTED or Contact:DUPLICATES_DETECTED will appear in the Batch Update Errors.

Can I schedule bulk updates?
Yes! You can schedule bulk updates in Apex Classes. See the Scheduling Bulk Updates section for more detailed instructions.

  • Scheduled ConnectLink jobs are currently unavailable for Professional and Group Editions. Users under this Salesforce licenses are advised to manually run Bulk Updates on a regular basis.

Does Agile overwrite existing data with blank or NULL values?
No. If data exists in a field and Agile doesn’t have a value for that data element, Agile will not overwrite the data with a blank value, regardless of the mapping preference.

Best Practices

Don’t forget about accounts/contacts that you do business with!

  • 25%+ turnover year over year in education.
    • 1,044,223 personnel changes/confirmations in September 2022.
  • Won’t know new/current job roles.
    • 199,547 people with new roles in September 2022.
  • Domain changes.
    • 599 domain changes in September 202.

Import new institutions.

  • Use the New Institutions tab for importing new accounts in your license.
    • 3,442 institutions created in September 2022.
  • For accounts created by end users, click the ConnectLink Account Matching button to append a ConnectLink Key and update the new account.
  • You can also search and import accounts one at a time on the Search tab.

Closed/inactive records.

  • Create a plan/process for purging inactive/closed records.
    • 119,838 people inactivated in September 2022.
    • 919 schools closed in September 2022.
    • DON’T purge people or accounts with opportunities/tasks/notes/etc. associated.
    • When prospecting/marketing, exclude inactive personnel from the lists.

Have ConnectLink Roles and ConnectLink Inactive Roles visible in related accounts/contacts object.

  • When running title-based reports, use the ConnectLink Roles to account for people with multiple roles.

Enable Match Educator Records on Email Address and map email address to the standard email address field for contacts (even if you want to set the preference to Salesforce). This allows the Match Educators on Email Address setting to work properly.

  • If preference is set to Salesforce, consider adding an additional email field, map Agile’s email address and prefer Agile Ed. This allows access to the Agile email if yours starts to bounce or if you aren’t getting engagement.

Install the latest version for additional functionality.

  • Add Report CL Data Problem button to account and contact layouts.

Schedule Bulk Updates weekly.

Agile has secondary K-12 hierarchies.

  • EMO/CMO
  • RESA

Custom deduplication recommendation.

  • Instead of using standard Salesforce account deduplication riles, use these criteria to create custom rules in order to make the all run more effectively. See image below for an example of what Salesforce identifies as duplicates with the standard duplicate rules.
    • NCES LEAID is the same AND RECORD_TYPE_TEXT = District WITH condition that RECORD_TYPE_TEXT = District
    • OR SCHNO is the same AND RECORD_TYPE_TEXT = Building WITH condition that RECORD_TYPE_TEXT = Building
    • OR FILE_TYPE_TEXT is the same AND RECORD_TYPE_TEXT is the same AND PHONE is the same AND MAILING_ADDR1_PROPER is the same
  • Standard Salesforce account deduplication rules:

Speak with a Consultant     |     866.782.0241 x 108     |     [email protected]

We use cookies to give you the best online experience. Cookies keep our site secure and reliable. They allow us to personalize agile-ed.com to you and help us analyze how the site is used.

Skip to content