Question:

Why are CRM Custom Keys not generated for records in Network?

Answer:

Through the integration between Network and CRM, oftentimes Custom Keys will be generated for Health Care Providers (HCPs), Health Care Organizations (HCOs), Addresses, and relationship records (PARENTHCOs). These Custom Keys will appear on records in the form of a Salesforce (SFDC) ID and should be accompanied by the defined System in Network that is being used for the Network-CRM integration.

Example Custom Key from CRM Org:

VCRM:Account:001K000001NEZ05IAH

The Custom Keys for HCPs and HCOs can be found in the External Identifiers section on the record's page.

Upon an Account's creation in CRM, whether through the Network Bridge or Network Account Search (NAS), the integration sends the SFDC ID to Network and adds this as a Custom Key to the appropriate HCP or HCO record. Additionally, should the HCP or HCO have been added via NAS in CRM, Custom Keys will be generated and added to the appropriate Address and/or PARENTHCO record(s).

Custom Keys will be added to records in Network if:

• The Account is created in CRM via Network Bridge
• The Account is created in CRM via Network Account Search (NAS)
• The Account is created in CRM via Data Change Requests (DCRs)
• Custom Keys will be added to Addresses and PARENTHCO records when the Account is created in CRM via NAS
• Custom Keys will be added to Addresses and PARENTHCO records when the Account, Address, and PARENTHCO is created in CRM via DCRs

Custom Keys will not be added to records in Network if:

• The Accounts are already created in CRM before existing as VALID or UNDER_REVIEW records in Network
• The Addresses and/or PARENTHCOs were added to CRM via Network Bridge

Resending records in Network Bridge jobs will not cause the creation of a CRM Custom Key for those records in Network. The only way to add the Custom Keys to those records will be to use a Source Subscription or adding them manually in the Network UI.

Please note that some exceptions to the above-mentioned behaviors can apply. For instance, integrating more than one CRM Org with the same Network instance can add additional SFDC style Custom Keys to records that already exist in one CRM Org but may have been added in the additional Org(s).

Example: