Lead Resource Not Marked As Primary When Adding The Resource To The Lead Via Import
(Doc ID 2177766.1)
Last updated on NOVEMBER 16, 2016
Applies to:Oracle Fusion Sales Cloud Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Leads, Sales Campaigns
The customer is adding a resource the Lead via File Import using the following mapping:
Lead_LeadNumber, LeadResource_ResourceId, LeadResource_FunctionalRole and LeadResource_PrimaryFlag
The import completes successfully but they notice the following issues:
1) The wrong user has been marked as primary.
2) The functional roles passed as part of import are not reflected on the UI.
Per the import mapping, the lead resource should be set as the primary and with the functional role provided in the import CSV file
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document