When creating the queue definition you can choose specific events under the Type Filter. I believe you can have multiple Queue configurations which publish to the same queue. The subscription which reads events is where you need to be mutually exclusive or you can run into issues if one subscription removed events intended for another subscription.
I think in your scenario you just need to define multiple configurations for each Event Type and Object Filter combination you need.
The Object Filter will limit the

Original Message:
Sent: 07-17-2023 11:17
From: Mark Burlock
Subject: SQS Streaming: Can Object Filter Include The Type of Event i.e. ENTITY_CHANGED - Not The Type Filter
Dan,
We've done it (and it's working) for the updatedBy attribute but that is under the "object" attribute parent.
The question here was can we do it for the "type": "ENTITY_CHANGED",
which is a sibling of the updatedBy and we want to do this in combination of the 2.
Thanks,
Mark
------------------------------
Mark Burlock
Dodge Data & Analytics
Hamilton NJ
Original Message:
Sent: 07-17-2023 10:06
From: Daniel Gage
Subject: SQS Streaming: Can Object Filter Include The Type of Event i.e. ENTITY_CHANGED - Not The Type Filter
I believe you can put an object filter on the event queue subscription. I would imagine something like:
not ( startsWith( updatedBy,'Automatic merge process at'))
I've never created a filter on the updatedBy property, but if it works then you should get the desired behavior. The filter can be added in Console | Tenant Management | External Queue admin interface.
------------------------------
Dan Gage
Principal Solution Consultant
Original Message:
Sent: 07-16-2023 20:13
From: Mark Burlock
Subject: SQS Streaming: Can Object Filter Include The Type of Event i.e. ENTITY_CHANGED - Not The Type Filter
I am looking to prevent SQS events from type ENTITY_CHANGED but only when the updatedBy attribute starts with a particular value.
Attributes included in the Object Filter all are under the "object" attribute which is fine for the updatedBy but does not allow filtering for the "type" of event which is a peer to the object attribute.
In the exampe below base on "type" equal to ENTITY_CHANGED and Not Starting with updatedBy
"type": "ENTITY_CHANGED",
"object": {
"uri": "entities/GI1JrY3z",
...
"updatedBy": "Automatic merge process at 2023-07-13",
...
For additional context, we are looking to do this to avoid non-necessary event traffic for an entity including referencedAttributeURIs where there is a merge on the entity being referenced. In this particular case:
Merge of an Organization
Extraneous Traffic for the Contact even though the OV value for the referenced attribute does not change
Thanks,
Mark
------------------------------
Mark Burlock
Dodge Data & Analytics
Hamilton NJ
------------------------------