PitchBook For MS Dynamics Plugin MS Dynamics AdMIN USER Guide All materials Confidential

Process overview Download the install package Setup Plugin User Credentials Customize MSD Page Layout Add PitchBook Widget to MSD Add PitchBook Fields to MSD Configure integration (See setup guide)

Why Does PitchBOok Need a ms dynamics Admin User? Dynamics Admin Rights are Required to Change Layout Automated Connection Testing Weekly Account PB Fields Synchronization Weekly Contact, Lead and Account Linkage & Sync Field Mapping Note: The plugin does not work without this user specified.

Minimum dynamics Admin RIGHTS Required The linked CRM credentials must have access to Create/Read/Write the following entities: Account Contact Lead The MS Dynamics user completing the installation must be able to install the PitchBook Web Resource The MS Dynamics user completing the installation must be able to add sections on pages and add fields to these sections. (System Customizer / System Administrator roles)

Client Authentication The first time credentials are saved in PitchBook they will be used to make initial connection to verify they are correct. If the connection is established successfully, PitchBook will retrieve MS Dynamics ID from Dynamics instance and will store it in PitchBook database. The Organization ID is a unique identifier for each Dynamics instance. It will be used to identify connections from the plugin and link it with the PitchBook license.

Test Connections Every time “Test Connection” is pressed in PitchBook, the credentials will be verified. Every day at 9 AM EST, PitchBook automatically tests the Admin Credentials by a simple login. In case of failure an email is sent to the designated user at your organization.

Weekly Contact, Lead and Account Linkage & Reconciliation (1/2) Every Sunday at 12 AM EST, PitchBook uses Dynamics Admin Credentials to extract all Accounts, Contacts and Leads that have been linked with PitchBook (have PitchBook ID field specified). It retrieves Dynamics IDs and PitchBook IDs and nothing else. It uses this information to reconcile local linkage data with the Dynamics database in case there is a discrepancy. This process can also be initiated on demand.

Weekly Contact, Lead and Account Linkage & Reconciliation (2/2) Every Saturday at 2 AM EST, PitchBook uses Dynamics Admin Credentials to extract all Accounts, Contacts and Leads that have not been linked with PitchBook (do not have PitchBook ID field specified). It retrieves Dynamics ID and Account Name for Accounts, runs an algorithm to match PitchBook entities and saves PitchBook ID for exact matches found for Accounts. All Account names retrieved by this process are deleted immediately and not stored by PitchBook. It retrieves Dynamics IDs and Email Addresses for contacts and leads, runs algorithm to match PitchBook people and saves PitchBook ID for exact matches found for Contacts & Leads. All email addresses retrieved through this process are deleted immediately and not stored by PitchBook.

Weekly Account PB Fields Synchronization Every Sunday at 5AM EST, PitchBook uses Dynamics Admin Credentials to synchronize PB Custom Fields from Accounts that were synchronized manually from PitchBook plugin. PitchBook does not retrieve any information from Salesforce during that process. It updates fields directly in Salesforce by using an API. Once an Account has been synced, it will continue to automatically update every week.

Field Mapping The first time a user accesses the Link or Sync pages inside the PitchBook plug-in, the Dynamics Admin Credentials are used to retrieve fields for Account, Contact and Lead objects with their types, descriptions and availability to access. It is used to create an initial mapping of PitchBook to Dynamics fields to be used during the Synchronization and Import processes.

MS Dynamics User Right Overrides Occasionally, Dynamics Admin Credentials can be used when trying to synchronize Dynamics objects with the PitchBook plug-in manually. This happens only when a user does not have access rights to Dynamics fields (most likely read-only) that have been specified in the mapping. For this particular case, Admin Credentials will be used to make these updates so the user can synchronize the record successfully.