<< Prev Question Next Question >>
Question 8/71
Universal Containers acquires several companies and decides to consolidate all customer service systems used by the acquired companies into one Salesforce Service Cloud. They decide to use an ETL to extract service requests from various systems, apply appropriate transformations, and load cases into Salesforce. Different requests captured by different customer service systems could belong to common accounts in Salesforce, so care must be taken to avoid creating duplicate accounts. Which two API options should be considered to load cases into Salesforce that would be safe from record -locking issues? Choose 2 answers
Recent Comments (The most recent comments are at the top.)
B & D
Answers should be B & D.
SFDC can add up to 200 records in a single create()call. If a create request exceeds 200 records, then the entire operation fails.
https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_apicalls.htm
https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_apicalls.htm
... to avoid creating!!!!! (Not query): Your client application can add up to 200 records in a single create() call. If a create request exceeds 200 records, then the entire operation fails.
"batch size can not be less than 200 for SOAP API" - not sure if that's true.
I think SF helper is a liar!
I think SF helper is lying.
B and C are correct because batch size can not be less than 200 for SOAP API.
D.
Your client application can add up to 200 records in a single create() call.