Editing the filteringattributes in an existing Dataverse Update/Create trigger breaks the Update part of the trigger. Replicating the behaviour should be fairly easy. First create a regular trigger without any optional attributes.
{
"inputs": {
"host": {
"connectionName": "shared_commondataserviceforapps",
"operationId": "SubscribeWebhookTrigger",
"apiId": "/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps"
},
"parameters": {
"subscriptionRequest/message": 4,
"subscriptionRequest/entityname": "phonecall",
"subscriptionRequest/scope": 4
},
"authentication": "@parameters('$authentication')"
}
}
In my case I used the phonecall entity. Creating a new phonecall and closing the the phonecall correctly triggers one create and one update flow run. After that I edited the existing trigger and added a new filteringattribute.
{
"inputs": {
"host": {
"connectionName": "shared_commondataserviceforapps",
"operationId": "SubscribeWebhookTrigger",
"apiId": "/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps"
},
"parameters": {
"subscriptionRequest/message": 4,
"subscriptionRequest/entityname": "phonecall",
"subscriptionRequest/scope": 4,
"subscriptionRequest/filteringattributes": "actualend"
},
"authentication": "@parameters('$authentication')"
},
"metadata": {
"operationMetadataId": "075318e8-eb44-46df-a2c9-3c2f2ce4a8f8"
}
}
Counterintuitively it now only triggers during the creation of a phonecall. Updates are never triggered. That includes closing the phonecall and just changing some irrelevant fields. Now edit the trigger again and remove the previously added filteringattribute.
{
"inputs": {
"host": {
"connectionName": "shared_commondataserviceforapps",
"operationId": "SubscribeWebhookTrigger",
"apiId": "/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps"
},
"parameters": {
"subscriptionRequest/message": 4,
"subscriptionRequest/entityname": "phonecall",
"subscriptionRequest/scope": 4
},
"authentication": "@parameters('$authentication')"
},
"metadata": {
"operationMetadataId": "075318e8-eb44-46df-a2c9-3c2f2ce4a8f8"
}
}
Now it triggers neither on create nor on an update operation. The only difference to the working configuration is the existence of the metadata. Is there some mistake I am making in my process? Or is this working as intended?
Kind regards
MG
