I have a Business Central version 14 with CU16 installed on premise.
My issue is that BC never sends notifications to my webhook endpoint. The subscription gets confirmed, but I never receive any notifications.
Currently, I only have a single webhook subscription on Items:
I can renew and delete the subscription just fine.
Whenever I update an item or more, nothing is sent to the specified notification URL.
I only receive notifications when I create or renew a subscription.
I've had issues with this previously - with CU04, webhooks didn't work. Spent a lot of time and money on a Microsoft Support ticket, just to learn that is was magically fixed somewhere between CU04 and CU10, since I got notifications while on CU10.
Now I'm on CU16 and now I don't get any notifications any more. I don't know if it related to the previous issue.
Anyone know how to resolve this issue?
I just wanted to chime in and say that we're experiencing this issue as well on version 17.0 on-premise. We're able to create and confirm the subscriptions, and also patch and delete. But we cannot get Business Central to actually send any notifications. The network guys are monitoring the traffic, and they can't see any traffic coming from Business Central. We've tested this on base application APIs and our own APIs.
And just to get the obvious pitfalls sorted out;
1. We can see the APIs listed when posting a Get request to the webhookSupportedResources end-point
2. We're not using temporary tables as source tables in our APIs
3. We're using id as OData key
4. We've checked the server instance that API subscriptions are enabled
5. Access and authorization issues should be sorted out (firewall, logon etc)
At the moment we're left with attempting to upgrade to version 17.1, but this obviously carries with it a cost and we're not even sure it will work as I can't see anything in the release notes from Microsoft suggesting they've done work on webhook subscriptions
Any help would be much appreciated
I've started a support case via the Microsoft Partner Portal. It seems like this is a reoccurring issue between major versions and cumulative updates. I have to say that it's rather scary that we can't expect documented functionality to work.
We upgraded the solution to version 17.1, but we still cannot get it working. We tried the webhookLogs and are getting an empty result same as you