Skip to main content

KI-38

Multiple Veeva Network Instances Are Not Supported

Key/Summary

KI-38 Multiple Veeva Network Instances Are Not Supported

Status

Done

Created

10/06/2020

Updated

12/17/2021

Description

Medical Information Cloud Inquiry Management does not support multiple Veeva Network instances. Even if multiple Veeva Network instances are connected to Medical Information Cloud Inquiry Management through MDM Connection custom metadata records, only account information from the default Veeva Network instance is pulled during the MIRF/Inbound Form process or when you select from Account Search.

Impacted Capabilities

Inquiry Management

Affected Apps

Medical Information Cloud - Classic

Medical Information Cloud - Lightning

Affects Versions

None

Fix Version

MIC V11

Steps to Reproduce

  1. In Medical Information Cloud Inquiry Management, create two MDM Connection custom metadata records to enable the application to search for accounts within two registered Veeva Network instances.

  2. In a Veeva Network instance that you did not set as the default connection in the previous step, identify an account.

  3. In Medical Information Cloud Inquiry Management, search for and select the identified account. Medical Information Cloud Inquiry Management attempts to pull the account information from the MDM connection that is under the default segment.

Workaround

Customers can create a custom account search handler to search multiple network instances. For information on how to configure account search handlers, refer to Veeva Network.