Exam PL-400 topic 2 question 38 discussion

The first one should be No, because the Retrieve method will take GUID as a parameter but given the function sending string as AccountID, the account needs to convert to GUID.

No - Second parameter for Retrieve shold be of type GUID. The example is using string type and, as there is not any implicit conversion from string to GUID, the method is not using correct parameters (https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.iorganizationservice.retrieve?view=dataverse-sdk-latest) No - The numberofemployees column is not being updated, so the plug-in won't be triggered No - if numberofemployees is null then GetAttributeValue<int> will return the default value for integer which is 0 (https://www.crmanswers.net/2015/04/getattributevalue-demystified.html) (https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.entity.getattributevalue?view=dataverse-sdk-latest#remarks). So, the condition will evalue 0 > 100 which won't throw an exception.

No Yes Yes. 1st one is you can't use string in place of GUID 2nd one if filtering attributes is set correctly, a plugin will fire after update 3rd one exception will be thrown. You can't compare null > 100 it will error.

1. No - using string instead of guid. 2. Yes - numberofemployees will get updated so any plugin attached to this field will run.\ 3. No - that is why it is recommended to use GetAttributeValue.

According to ChatGPT, when given the code and the fact that the accountId is NOT cast as a GUID, the code could still run: ChatGPT Answer: In summary, while the plugin code itself does not explicitly cast accountId to a Guid, the success or failure of the code execution will depend on the validity of the accountId string as a GUID representation.

Shouldn't the second option be "Yes" accoring to Microsoft documentation ?: "You should avoid retrieving all columns in a query result because of the impact on a subsequent update of records. In an update, this will set all field values, even if they are unchanged, and often triggers cascaded updates to child records" https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.query.columnset.allcolumns?view=dataverse-sdk-latest

No to all

First one is "Yes" , you can find the same code at the page below. Entity entity = svc.Retrieve("account", accountid, new ColumnSet("name")); https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/entity-operations-retrieve

No for all

I think it should be No, Yes and No. For second one, there seems to be some missing context. But with waht is being mentioned, Yes seems to be correct

Sentence 1: No https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/entity-operations-retrieve Sentence 2: No A plugin on update will trigger only if filter attributes are not used which is not best practice. Also using Retrieve with ColumnSet(True) is not best practice, however the parameters are correct. Sentence 3: No https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.entity.getattributevalue?view=dataverse-sdk-latest

answer is NO , YES,YES.

A plugin on update will trigger only if filter attributes are not used which is not best practice. Also using Retrieve with ColumnSet(True) is not best practice, however the parameters are correct.

if they use columSet(true) every plugin on update of the record will trigger, even if it's value does not changes. Make the test by yourself: Create a plugin that take a value and make it value += 1 on update of another field and make a "columnSet(true)" with an update later...

maybe the first one is correct if its GUID as shown in here https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/entity-operations-retrieve#basic-retrieve