Custom Import Restricting Loading Multiple Team Members, Duplicates Are Flagged When They Shouldn't (Doc ID 2503449.1)

Last updated on JUNE 08, 2023

Applies to:

Goal

I'm trying to import to a custom object, Member, as part of our move to production.

On our dev1 site I am using Import Activity 'Load RFA Team'. On the system itself we can manually load multiple teams members for each RFA Queue. If I try to do this in the import I get the following message: A duplicate record exists in the current import batch. (MKT-285223) Cause: A duplicate record exists in the same batch with the target object attribute value. Action: Remove the duplicate record from the import batch, or update the record so that it is no longer a duplicate of another record in the import batch.

We have over 1500 records to load and this was never successfully done by Apex for us.

How can I remove the constraint on the import since it does not exists in the system itself.
I am loading the Member record which is a child of RFA Queue.
In the 'Load RFA Activity' import activity you can see when the input file RFATeamTestLoad file is used that duplicates are flagged when trying to add more than one member to an RFA Queue. When input file RFAPartialTeamLoad is used with only 1 member per queue it completes successfully. We will always have more than 1 member per RFA Queue and need the restraint removed for our initial load.

Even though the import using the RFATeamTestLoad indicates a failure and shows 0 records uploaded successfully that the users were all added to the member record for the respective RFA Queues. Can I expect this to work for the rest of our loads and should I be ignoring the error message and indicator that says 0 records were loaded due to duplicate records?
 

Solution

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