Skip to Content

PL-400: Which Attribute Should You Check for Contact Lookup Data in Dataverse Using OData?

How to Verify Related Table Data in Dataverse with _pref_contactid_value Attribute?

Table of Contents

Question

A company has a custom table named TableA that has the following characteristics:

  • a lookup field to the contact table
  • schemaname is pref_ContactId
  • logicalname is pref_contactid
  • related to another custom table named TableB

You are developing an onLoad JavaScript function for TableB. The function must check whether the contact lookup on the related TableA contains data. You are using web API and Open Data Protocol (OData) to get the related record.

You need to check the response from web API.

Which attribute should you check?

Select only one answer.

A. pref_ ContactId
B. pref_ contactid
C. _pref_ContactId_value
D. _pref_contactid_value

Answer

D. _pref_contactid_value

Explanation

This item tests the candidate’s knowledge of the OData web API.

When a lookup is selected using the web API, the result will contain _<logicalname>_value. In this example, this means _pref_contactid_value.

pref_ContactId is incorrect because it is missing the leading underscore and the trailing underscore value. It is also using the schemaname instead of the logicalname.

pref_contactid is incorrect because it is missing the leading underscore as well as the underscore value at the end.

_pref_ContactId_value is incorrect because it is using the schemaname instead of the logicalname.

Microsoft Power Platform Developer PL-400 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Microsoft Power Platform Developer PL-400 exam and earn Microsoft Power Platform Developer PL-400 certification.