Recently we were writing a plugin that on the creation of a lead updates the originating lead of a contact record. The value was neither getting updated nor we were getting any errors.
It was after we spent a good amount of time debugging, realized that this field cannot be updated.
So basically, we can specify a value for it during create of contact but cannot update it.
Hope it helps..
Recently we were working on Facebook Leads integration with Dynamics 365. Webhook for Leads can be configured to send real-time notifications of the Leads ads changes.
The first step of setting up Webhook requires creating an HTTPS endpoint that can process 2 types of HTTP Requests – Verification and Event notifications.
Here we will see how to configure the Power Automate flow for verification.
Login to Meta for Developers – Facebook and create an app.
https://developers.facebook.com/
Select Business for the app type.
After the App is created, select Webhooks to be added to the app. Click on Set up.
Next click Subscribe to this object. Here we have User selected.
For getting leads notification we need to select Page
And subscribe to leadgen object
It asks us to specify the Callback URL and Verify token.
Back in Power Automate create a Flow with Request type Trigger, followed by Parse JSON and Response actions.
For HTTP Request, select GET as the method, as FB will send a GET request to the endpoint URL, with the verification requests included in the endpoint of the URL.
Next, Parse the JSON and specify the Content and Schema
Content –
triggerOutputs()['queries']
Schema –
Lastly in Response, set Status Code as 200 and Body as hub.challenge.
Here FB expects the Endpoint to verify the hub.verify_token (which we haven’t set up yet) and respond with hub.challenge value after verification.
Save the Flow, and copy the URL generated for the HTTP Request trigger.
Back in Meta for Developers, in edit user subscription paste the Callback URL and for now in place of token specify any value and click on Verify and Save.
We should now have a Webhook endpoint (Flow) successfully configured
We can also see our Flow ran successfully.
Here in the example we configured the webhook validation for User events, for Facebook Lead we need to configure it for Page, the other options available are Permissions, Application, Instagram etc.
Please check –
https://powerautomate.microsoft.com/nl-nl/blog/connect-facebook-workplace-to-sharepoint/
Hope it helps..
{
"type": "object",
"properties": {
"hub.mode": {
"type": "string"
},
"hub.challenge": {
"type": "string"
},
"hub.verify_token": {
"type": "string"
}
}
}
We might get the below error while using Xrm.WebAPI.
‘Bad Request – Error in query syntax.’
One of the reasons could be that while setting up the Lookup field, we haven’t removed the curly brackets.
Use the below function to replace/remove them.
Hope it helps..
Dynamics Marketing JavaScript API is only available for the marketing form hosted as Script. It is not available for forms hosted as Iframe.
More on embedding form on external page – https://nishantrana.me/2022/11/10/how-to-embed-marketing-form-on-an-external-page/
Add a reference to form-loader.js or load.js to access the API.
Below is our form with a hidden field in it.
Based on the current living situation (drop down), we want to set the value of the Financially Capable field (bool) – the hidden field’s value as either True or False.
For this, we have added the below script, in the formSubmit event.
formSubmit triggers on form submit before the form submission is sent to the server.
Check all the events here – https://learn.microsoft.com/en-us/dynamics365/marketing/developer/marketing-form-client-side-extensibility#form-events
The script – Get the id of the element through browser’s developer tools.
Hope it helps..
// Extending Marketing form with code
// formSubmit - Triggers on form submit before the form submission is sent to the server.
MsCrmMkt.MsCrmFormLoader.on('formSubmit', function (event) {
// get the id of the elements through developer tools of the browser
// based on selected current living situation (optionset)
if (document.getElementById('deb110aa-e266-ed11-9561-000d3ae090c0') != null) {
var selectedCurrentLivingValue = document.getElementById('deb110aa-e266-ed11-9561-000d3ae090c0').value;
if (selectedCurrentLivingValue == 881990000) {
// set the value of Financially Capable field (boolean)- true / false
document.getElementById('dcc46e64-2867-ed11-9561-000d3ae090c0').value = "1";
}
else {
document.getElementById('dcc46e64-2867-ed11-9561-000d3ae090c0').value = "0";
}
}
});
Recently while designing the marketing form, we realized the Hide field option missing for our dropdown fields.
There are 2 ways to solve this –
In the HTML designer mode for the Marketing form –
The field will be hidden but the Hide field toggle won’t be available in the designer.
This adds the Hide field toggle option in the designer.
The result –
The helpful thread – https://community.dynamics.com/365/marketing/f/dynamics-365-for-marketing-forum/391470/how-do-i-populate-lead-source-from-a-hidden-field-on-marketing-form
Hope it helps..
We can see the Account Insights / Contact Insights tab added along with LinkedIn Lead Info on the default lead form (as well as contact/account) after we install Dynamics 365 Marketing.
These tabs will be added if you try creating a new form (Main).
But if we have other existing forms (Main), these tabs won’t be added and won’t be available for us to add.
In that case, we need to edit the Form XML to add these sections.
Here we will be adding the Contact Insights tab to one of the existing forms to the Lead.
Using the Form XML Manager (XrmToolBox plugin – developed by my friend Rasheed), get the Form XML of the form where we have the contact insights tab added.
Copy the below details –
Tab – Contact Insights
And the below controlDescription
Going back to Form XML Manager, select the form where we want to add the contact insight tab, get its Form XML and add the above details and publish.
We can see the Contact Insights tab added
Similarly, we can Account Insights, and the LinkedIn Lead Info tab as well.
Hope it helps..
<tab name="contactInsights" id="{AC28F8C9-4498-47C7-8D9B-2FE028CFBDAC}" IsUserDefined="0" locklevel="0" showlabel="true" expanded="true" labelid="{6905336d-985b-4137-a106-31b1dd4e1560}">
<labels>
<label description="Contact insights" languagecode="1033" />
</labels>
<columns>
<column width="100%">
<sections>
<section name="insights_section" showlabel="false" showbar="false" locklevel="0" id="{2328D81F-CA70-4A20-8B62-DA36756DA7D8}" IsUserDefined="0" layout="varwidth" columns="1" labelwidth="115" celllabelalignment="Left" celllabelposition="Left" labelid="{29474d06-89ea-41ad-a999-9d96dd95c938}">
<labels>
<label description="Insights" languagecode="1033" />
</labels>
<rows>
<row>
<cell rowspan="1" id="{37367a00-f45e-4ae4-a4a4-5ba1023fdc11}" colspan="1" labelid="{e971ab6b-ea22-4543-bbd5-06e50f11f9f1}">
<labels>
<label description="" languagecode="1033" />
</labels>
<control id="msdynmkt-lead-insights-banner-control" classid="{F9A8A302-114E-466A-B582-6771B2AE0D92}" disabled="false" uniqueid="{B93040CC-F97E-48D8-8166-5179C8C942CE}" isunbound="true">
<parameters />
</control>
</cell>
</row>
<row>
<cell id="{58B703D6-BBA5-4078-9499-1D5A1FB35932}" showlabel="false" locklevel="0" labelid="{db0b8895-c098-45e5-b95f-f85df882f96d}">
<labels>
<label description="Insights" languagecode="1033" />
</labels>
<control id="LeadContactInsightsCtrl" classid="{F9A8A302-114E-466A-B582-6771B2AE0D92}" datafieldname="msdyncrm_insights_placeholder" disabled="false" uniqueid="{ADB58B3F-E8A8-432B-BF8C-08196D8F87ED}" />
</cell>
</row>
</rows>
</section>
</sections>
</column>
</columns>
</tab>
<controlDescription forControl="{ADB58B3F-E8A8-432B-BF8C-08196D8F87ED}">
<customControl formFactor="0" name="MscrmControls.InsightsControl.InsightsControl">
<parameters>
<configuration static="true" type="SingleLine.Text">LeadContactInsights</configuration>
</parameters>
</customControl>
<customControl formFactor="1" name="MscrmControls.InsightsControl.InsightsControl">
<parameters>
<configuration static="true" type="SingleLine.Text">LeadContactInsights</configuration>
</parameters>
</customControl>
<customControl formFactor="2" name="MscrmControls.InsightsControl.InsightsControl">
<parameters>
<configuration static="true" type="SingleLine.Text">LeadContactInsights</configuration>
</parameters>
</customControl>
</controlDescription>
<controlDescription forControl="{48D797ED-2F85-4D89-A329-69C2A1A0E1DD}">
<customControl formFactor="0" name="MscrmControls.InsightsControl.InsightsControl">
<parameters>
<configuration static="true" type="SingleLine.Text">LeadAccountInsights</configuration>
</parameters>
</customControl>
<customControl formFactor="1" name="MscrmControls.InsightsControl.InsightsControl">
<parameters>
<configuration static="true" type="SingleLine.Text">LeadAccountInsights</configuration>
</parameters>
</customControl>
<customControl formFactor="2" name="MscrmControls.InsightsControl.InsightsControl">
<parameters>
<configuration static="true" type="SingleLine.Text">LeadAccountInsights</configuration>
</parameters>
</customControl>
</controlDescription>
<controlDescription forControl="{B93040CC-F97E-48D8-8166-5179C8C942CE}">
<customControl formFactor="0" name="CxpOrchestrationAnalytics.InsightsBannerControl.InsightsBannerControl">
<parameters />
</customControl>
<customControl formFactor="1" name="CxpOrchestrationAnalytics.InsightsBannerControl.InsightsBannerControl">
<parameters />
</customControl>
<customControl formFactor="2" name="CxpOrchestrationAnalytics.InsightsBannerControl.InsightsBannerControl">
<parameters />
</customControl>
</controlDescription>
</controlDescriptions>
Nishant Rana's Weblog 