Exam PL-400 topic 7 question 1 discussion

No scenario can be yes, because the value of the lastname field is overwritten with the value of "Doe". All duplicate evaluation with the combination of alternate keys is done with the latter value.

The code is wrong in many ways. Working code : Entity contact = new Entity() { LogicalName = "contact", KeyAttributes = { {"lastname", "Smith" }, {"clientnumber", "abc123" } } }; contact["lastname"] = "Doe"; UpsertRequest updcontact = new UpsertRequest() { Target = contact }; UpsertResponse response = (UpsertResponse)crmService.Execute(updcontact);

Syntax is wrong in multiple places, but even if we assume that it is correct. Answers are still No for all. Last name is being changed to "Doe" before the Upsert

Don't understand the purpose of such questions. Technically all are No.

No for all

For me its NNYN

So NO ONE just TEST it???? There will be an error if you use none-key-attribute in KeyAttribute only when xxx (try it plz). It is not the behavior said in MS doc, very disappointment.

Should be NO for all

when created - Attribute is priority when updated - Key is priority No - Create - attribute is priority, so Deo Yes - Update - Key is priority - Smith Yes - Update - Key is priority - Smith No - Create - attribute is priority, so Deo

1) NO: Record does not exist -> CREATE -> attributes have prio - last name will be doe 2) YES: Record does exist -> UPDATE -> key-attributes have prio - last name will be Smith 3) Undecided: For this to be possible at all, client number must be an alternate key too! So it clearly depends on wether the combination already existed (YES) or not (NO) 4) NO: Record does not exist -> CREATE -> attributes have prio - last name will be doe

No scenario can be yes

Correct answer: No: attributecollection has prio over keyattributes, so the created contact would have doe Yes: No change to the exisitng contact, so same as before Yes: one or multiple contacts found, doesn't matter, stored value stays the same No: Same as first question, a newly created contact would be named Doe

I would go with all No's because the lastname is overwritten to "Doe"

Whole code pobably crash on line 10 with "There is no key in the dictionary:...

>> If you specify a column set that is not defined as a unique key, an error will be thrown indicating that use of unique key columns is required. So AK must consist of two columns for this code to work, doesn't it?

Should the answer be YES, NO, NO, YES? The reason https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-upsert-insert-update-record Understanding the Upsert process: 1. Send UpsertRequest with enough data for a create or insert operation. 2. Dataverse will look up the record targeted by the target table. 3. If the record exists: a. Set the ID property of the target table with the ID of the found record. b. Call Update. c. Set the RecordCreated to false. ... 4. If the record doesn’t exist: a. Copy any alternate key values into the target table columns. b. Call Create. c. Set the RecordCreated to true. ... Finally in the scenarios where we do CREATE record - the lastname WILL BE "Smith" And where we do UPDATE record - lastname will be "Doe"