My Oracle Support Banner

EAI Not Setting Primary MVG For 1:M Link (Doc ID 808319.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Siebel Life Sciences CRM - Version 8.0 [20405] and later
Siebel CRM - Version 8.0 [20405] and later
Information in this document applies to any platform.
***Checked for relevance on 06-JAN-2011***


The 'Upsert' method of 'EAI Siebel Adapter' was invoked for Multi Value fields 'Alternate Phone#' and 'Address Name' using the Integration Objects (IO) 'CIFContact' and 'Internal Account Interface' respectively. In the IO 'CIFContact', Contact_Alternate Phone' is an Integration Component based on the 1:M Multi Value Link 'Alternate Phone'. In the IO 'Internal Account Interface', Account_Business Address is an Integration component based on the M:M Multi Value Link (MVL) 'Business Address'

It was observed that when the 'Upsert' operation was invoked on the Multi Value Fields (MVF) without passing the property 'IsPrimaryMVG' in the input xml, the first record was selected as the Primary in case of the MVG based M:M link ( i.e Busines Address) while in case of  the MVG based on1:M (i.e Alternate Phone) there was NO Primary was selected automatically.

The above behaviour was also reproducible with a different IO i.e 'Internal Contact Interface' and for both values of Auto Primary (Default and None) for the underlying MVLs.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.