Answered

Deployment of web hook registration

(0) Share

Report

Posted on by KimB

we have a web hook registration launching an HTTP triggered flow in MS Power Automate. Web Hook registrations and the related steps (created via Plugin Registration tool) are being added into the solution.

When we export the solution, we find back the web hook and steps in the customizations.xml.

However, the URL of the web hook registration refers to a URL in the dev environment. The querystring parameters don't seem to be part of this.

How can you properly deploy such types of Service Endpoints? How to make the Service Endpoint point to the right MS Flow environment/Flow endpoint.

Kind regards

Kim

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

v-yutliu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi @KimB ,

Because a webhook is a kind of service endpoint you can also invoke it without registering a step with a plug-in or workflow activity in the same way you can for an Azure Service Bus endpoint. You need to provide the ServiceEndpointId to the IServiceEndpointNotificationService interface. See the following Azure Service Bus samples for more information:

Sample: Azure aware custom plug-in

Sample: Azure aware custom workflow activity

I think maybe these docs may help you a lot:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/use-webhooks

https://docs.microsoft.com/en-us/sharepoint/dev/apis/webhooks/webhooks-reference-implementation

Best regards,

Was this reply helpful? Yes No
Verified answer

David Jennaway 716 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately there is not yet a good way to parameterise the plugin configuration data, so that it can automatically pick up environment-specific values.
For web hooks, your only real options are either changing the customization.xml, or writing a process to update the configuration data after import.
Or you could create a plugin that read data from a custom entity that stores the configuration values, and then makes a call to the service endpoint, though that's necessarily more development effort than using a web hook

Was this reply helpful? Yes No
KimB 32 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the feedback!

This also confirms my own analysis on this topic. Since authvalue (query string params) are not part of the customizations.xml, and we want to keep things low code, I will check the option to update the values afterwards.

I have logged the idea Better support for Service Endpoint registation deployment so a better deployment option can be considered.

Was this reply helpful? Yes No