Overview:
Customer encountered while using the new feature released in the System Administration section: Event API enhancement for Data Change Requests (DCRs) with Object Filtering.According to the release notes, the objectType attribute has been added to DCR event messages, allowing us to filter events for specific entity types in outbound streaming
Problem:
To utilize this feature, user configured the queue for CHANGE_REQUEST_CREATED and initiated the DCR from the UI. However, noticed that the messages are not being generated in the queue for this event.
Solution:
- Step 1:
-
In the SQS queue , we need to add "changes" field under JMSEventsFilteringFields and also have Object type
-
"streamingConfig": {
"streamingEnabled": true,
"streamingAPIEnabled": true,
"analyzeOvChanges": false,
"emptyStartEndRelationCrosswalks": false,
"largeObjectsSupport": false,
"skipPayload": false,
"payloadType": "SNAPSHOT",
"ovOnly": false,
"JMSEventsTimeToLive": 3600000,
"JMSEventsFilteringFields": [
"attributes.firstName",
"updatedTime",
"updatedBy",
"createdBy",
"changes",
"createdTime",
"attributes.lastName",
"type",
"uri"
],
"JMSIncludeMergeTime": false,
"messaging": {
"destinations": [
{
"payloadType": "SNAPSHOT_WITH_DELTA",
"ovOnly": false,
"type": "queue",
"provider": "aws://:[]@us-east-1",
"name": "",
"dtssQueue": false,
"groupingQueue": false,
"dataPipelineQueue": false,
"enabled": false,
"typeFilter": [
"CHANGE_REQUEST_CREATED",
"CHANGE_REQUEST_CHANGED",
"CHANGE_REQUEST_REMOVED"
],
"format": "JSON",
"JMSEventsFilteringFields": [
"objectVersion",
"attributes.FirstName",
"attributes.LastName",
"createdBy",
"commitTime",
"changes",
"createdTime",
"type",
"uri",
"objectType"
]
},
{
Comments
Please sign in to leave a comment.