Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam CRT-251 Topic 7 Question 84 Discussion

Actual exam question for Salesforce's CRT-251 exam
Question #: 84
Topic #: 7
[All CRT-251 Questions]

A consultant for Cloud Kicks is migrating data from an on-premise system to Salesforce. The consultant has imported.

Account records, and is attempting to import the associated Contacts using Data Loader, but the import has failed records. The error messages all read UNABLE TO LOCK ROW,

What could be causing these records to fail?

Show Suggested Answer Hide Answer
Suggested Answer: A

The most likely cause of the records failing is that updates to child records that have the same parent record are being processed simultaneously. This can cause the records to fail because child records must be imported after the parent records have been imported, and if the parent record is being updated at the same time as the child records, the import will fail. The other options are not likely to be the cause of the failed import.


by Viola at May 08, 2024, 06:00 PM

Limited Time Offer

25%

Off

Get Premium CRT-251 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Dana
6 months ago
Option C is the way to go. Apex Triggers, the bane of Salesforce admins everywhere. I feel the consultant's pain.
upvoted 0 times
Quentin
5 months ago
The consultant should work with the Salesforce admin to review and potentially disable any triggers causing conflicts.
upvoted 0 times
...
Reta
5 months ago
It's important to check for any triggers that might be interfering with the import process.
upvoted 0 times
...
Elly
5 months ago
I agree, Apex Triggers can definitely cause issues during data imports.
upvoted 0 times
...
Lavelle
6 months ago
The consultant should work with the Salesforce admin to review and potentially deactivate any triggers causing conflicts.
upvoted 0 times
...
Dannie
6 months ago
It's important to check if there are any triggers firing on the Account object that could be causing the problem.
upvoted 0 times
...
Graham
6 months ago
I agree, Apex Triggers can definitely cause issues during data imports.
upvoted 0 times
...
...
Virgina
6 months ago
I doubt D. If it was permissions, it wouldn’t specifically give a 'UNABLE TO LOCK ROW' error. More likely A or C.
upvoted 0 times
...
Sherrell
6 months ago
Haha, I bet the consultant is wishing they had a magic wand to just wave and make those UNABLE TO LOCK ROW errors disappear. Good luck with that!
upvoted 0 times
...
Kayleigh
6 months ago
What about D? Could it be incorrect permissions?
upvoted 0 times
...
Justa
7 months ago
I'm going to have to go with option C. The consultant should check for any active triggers on the Account object that might be causing issues with the Contact import.
upvoted 0 times
...
Georgiana
7 months ago
The correct answer is C. An Apex Trigger on the Account object is definitely the culprit here. Those things can be such a pain sometimes.
upvoted 0 times
Chun
5 months ago
No, I believe the problem lies with an Apex Trigger firing on the Account object during the import.
upvoted 0 times
...
Estrella
6 months ago
I think the issue might be related to updates happening simultaneously on child records.
upvoted 0 times
...
Providencia
6 months ago
No, I believe the problem lies with an Apex Trigger firing on the Account object during the import.
upvoted 0 times
...
Melissa
6 months ago
I think the issue might be related to updates happening simultaneously on child records.
upvoted 0 times
...
Nina
6 months ago
It's important to always check for any triggers that could be interfering with the process.
upvoted 0 times
...
Fausto
6 months ago
I agree, Apex Triggers can definitely cause issues with data imports.
upvoted 0 times
...
...
Bambi
7 months ago
C makes more sense to me. Maybe an Apex Trigger is causing the failure when Contacts are inserted, leading to a lock.
upvoted 0 times
...
Angelica
7 months ago
I think the issue could be an Apex Trigger on the Account object. Those pesky triggers can really mess up your data imports if not handled properly.
upvoted 0 times
Ronna
6 months ago
C) An Apex Trigger on the Account object is firing on insert and causing the Contact import to fail.
upvoted 0 times
...
Lea
6 months ago
A) Updates to child records that have the same parent records are being processed simultaneously.
upvoted 0 times
...
...
Bonita
7 months ago
I thought B initially, but Account records and Contact records should be imported in separate batches.
upvoted 0 times
...
Eugene
7 months ago
Yes, I have. I think it could be option A. When multiple updates happen on child records with the same parent, it can cause this issue.
upvoted 0 times
...
Virgina
7 months ago
Has anyone faced the 'UNABLE TO LOCK ROW' error while importing Contacts in Salesforce?
upvoted 0 times
...

Save Cancel