cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Regular Visitor

Deployment of web hook registration

Hi

 

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

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

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

View solution in original post

3 REPLIES 3
Highlighted
Community Support
Community Support

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:

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,

Community Support Team _ Phoebe Liu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted

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

View solution in original post

Highlighted

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.

 

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Users online (7,909)