Skip to main content

Lookup In Select of URL For Power Pages

 While working on a Power Pages implementation I was consume the Power Pages API to get a Lookup table so I could show and hide information on the form using jQuery.  One issue I was having is I couldn't get a lookup field to return even though I had it as a field in the site setting for the table and included it in the my select statement in the URL.  I kept getting an `unexpected error occurred`.

This issue is caused because lookup's are made up using 3 fields.

1) Formatted Value = The information you see in the lookup field (i.e. the record name)

2) Logical Name = The table the related record is a part of

3) Id = The id of the related record

In the api there is a 4th field that is returned that is the Associated Navigation Property and it is the logical name of the lookup field.

When setting up our select and even saying what columns can be returned in the API, we have to think how the OData endpoint will return the data to us.  The easy way to do this with a lookup is to add a `_` to the beginning of the field schema name and append `_value` to the end of the schema name.

Example:

`_new_lookupField_value`

Place that value in the fields site setting for the enabled endpoint, if not using `*` and add it to your select statement in the URL.  You should see the error go away and you should see returned data similar to this 


 {  
      "@odata.context": "https://myportal.powerappsportals.com/_api/$metadata#new_example(new_name,_new_lookupField_value)",  
      "@Microsoft.Dynamics.CRM.totalrecordcount": -1,  
      "@Microsoft.Dynamics.CRM.totalrecordcountlimitexceeded": false,  
      "@Microsoft.Dynamics.CRM.globalmetadataversion": "3068318",  
      "value": [  
           {  
                "@odata.etag": "W/\"3066510\"",  
                "new_name": "Example Name",  
                "_new_lookupField_value@OData.Community.Display.V1.FormattedValue": "Example Lookup",  
                "_new_lookupField_value@Microsoft.Dynamics.CRM.associatednavigationproperty": "new_LookupField",  
                "_new_lookupField_value@Microsoft.Dynamics.CRM.lookuplogicalname": "new_relatedTable",  
                "_new_lookupField_value": "2a9c7024-7ca0-4707-f086-419f27c27541"  
           },{  
                "@odata.etag": "W/\"2610804\"",  
                "new_name": "Example of Null",  
                "_new_lookupField_value": null  
           }  
      ]  
 }
In the above JSON there are two records returned.  One where the lookup contains data and one where it is empty.
Labels:

Comments

Post a Comment

Popular posts from this blog

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if ...
22 comments
Read more

Dynamics Set IFrame URL - D365 v8 vs. D365 v9

While doing client work, I came across a problem with setting an IFrame URL dynamically.  The underlying issue was that the sandbox instance is on v8 of Dynamics 365 and production is on v9 of Dynamics 365.  The reason for this was because this client was setup around the time that Microsoft rolled out v9.  Anyways, JavaScript that I wrote to dynamically set the URL of the IFrame wasn't working in the v9 instance.  This was because of changes that Microsoft made to how IFrames are loaded on the form and also changes to JavaScript. Here is my v8 setup: JavaScript runs OnLoad of contact form.  This works because of how IFrames are loaded in v8.  You can also run it on either a tab change (hide / show) or OnReadyStateComplete event of the IFrame.  Depending on your setup you will need to choose which is best for you.  For me in this case it was the OnLoad event. Here is the JavaScript: function OnLoad() { //Get memberid var...
26 comments
Read more

Effective Logging in Microsoft Dynamics 365 Plugins: Best Practices and Examples

Microsoft Dynamics 365 is a powerful suite of business applications that provides organizations with tools for managing customer relationships, sales, and operations. One of the essential aspects of developing custom plugins for Dynamics 365 is proper logging to ensure smooth functionality and easy debugging. In this blog post, we'll discuss best practices for logging in Microsoft Dynamics 365 plugins and provide examples to help you implement effective logging in your custom solutions. Understanding the Plugin Trace Log Microsoft Dynamics 365 provides a built-in logging mechanism called the Plugin Trace Log. The Plugin Trace Log can be used to record custom messages, exceptions, and other information for debugging purposes. To enable the Plugin Trace Log, follow these steps: Navigate to Settings > Administration > System Settings. Under the Customization tab, locate the "Plugin and Custom Workflow Activity Tracing" section. Set the option to "All" or ...
1 comment
Read more