If you haven’t heard or seen the most recent update to the SDK tool Configuration Migration Tool (CMT) then it is a must check out as the latest version of the tool includes filtering capaibility as Alan Mervitz (@amervitz) noticed on Twitter and has documented on his blog.
This feature in CMT has been long sought after for years…and years. The basics of the ask were, filter the data prior to exporting, so that you could extract a subset of data. Previously CMT worked in a fashion for an entity that it was all the records or nothing. You can 100,000 contacts in your system, it would attempt to extract all of them. Now you can provide a Fetchxml filter to a data schema definition and have that applied when CMT requests the data from CDS (also known to some as Dynamics 365/CRM…still). You could previously post process exports…
Open the Form page and copy the script to host the form.
On the host page, let us submit the details.
Back in our Marketing form, we can see the submission.
And also, both the lead and contact records created.
Now let us try one more submission without specifying a value for the lastname field (which it was showing in the notification, as a required field to be added on the form, for both the lead and contact table).
We can see the submissions in the Marketing Form.
And both the lead and contact records were created.
So although it shows the notification for all the mandatory fields which are not added in the form and marked as required, it still allows the record to be created.
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.
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
Recently we were getting the below error on the Omnichannel Ongoing Conversations Dashboard.
As the user was having an Omnichannel Administrator role, we expected it to work for the user. We raised a support ticket for the same and got to know that we need to assign the Omnichannel supervisor role for it to work for the user.
After assigning the Omnichannel supervisor role, the report started working for the user. Try it in incognito mode or clear the cache after assigning the role.