Start a new topic
Discussions xDM xDM - Integration
Answered

AuthoringType for Golden Record inNamed Query for Data Notification

I want to include AuthoringType of GoldenRecord in a Named Query so the Data Notificaiton send its as a property in JSON payload. However, when I add this attribute and deploy the named query, Data Notification sends a Validation error
ViewType GD is not valid for Named Query. The viewType I am selecting is Golden.
CAn someone help me to get the value from SA viewtype for golden record.

I want to trigger the notification when a field in golden record is edited.

Thanks

Best Answer

Hi Aishwarya,

thank you for the detail.

AuthoringType is a technical, built-in SemQL attribute, but it is only exposed on the Source Authoring views - SA, SA4L, and SAWE. It is not exposed on GD (Golden Data). AuthoringType describes how a specific source-authoring record was created (OVERRIDE vs. DATA_ENTRY), which is a source-level concept - a Golden Record can be built from several master/source-authoring records, each with its own authoring type, so there is no single "golden-level" value to expose.

That's why the model validation rejects it as soon as your Named Query's View Type is set to GD (Golden) - the attribute simply doesn't exist in that view.


Your stated goal is: trigger a notification whenever a field on the golden record is edited. Data Notifications don't rely on AuthoringType to detect that - they're driven by Batch ID ranges on the view you select. As long as your Named Query is filtered with the standard:

BatchID > :QUERY_PARAM_PREVIOUS_BATCH and BatchID <= :QUERY_PARAM_CURRENT_BATCH

on the GD view, any batch that creates or updates a golden record (including overrides made through authoring) will already be picked up and sent - you don't need AuthoringType in the payload to make the trigger work.

If you still want to expose "how this golden value was set" in the payload

If the real requirement is to tell consumers whether the change was an override vs. a new entry, you have an option, since the technical attribute can't be pulled onto GD directly:

Add a custom attribute to the entity (e.g., LastAuthoringType) and populate it via a post-consolidation enricher/rule that copies the value from the relevant SA record(s) into the golden/master record during certification. This is the standard workaround used for other SA/SD-only technical fields (e.g., PublisherID, SourceID) when they need to be surfaced at golden level.

This approach lets you keep your Named Query at GD view type while still surfacing authoring-type information in the notification payload.

Thanks and Best regards,
Haashim

1 Comment
Answer

Hi Aishwarya,

thank you for the detail.

AuthoringType is a technical, built-in SemQL attribute, but it is only exposed on the Source Authoring views - SA, SA4L, and SAWE. It is not exposed on GD (Golden Data). AuthoringType describes how a specific source-authoring record was created (OVERRIDE vs. DATA_ENTRY), which is a source-level concept - a Golden Record can be built from several master/source-authoring records, each with its own authoring type, so there is no single "golden-level" value to expose.

That's why the model validation rejects it as soon as your Named Query's View Type is set to GD (Golden) - the attribute simply doesn't exist in that view.


Your stated goal is: trigger a notification whenever a field on the golden record is edited. Data Notifications don't rely on AuthoringType to detect that - they're driven by Batch ID ranges on the view you select. As long as your Named Query is filtered with the standard:

BatchID > :QUERY_PARAM_PREVIOUS_BATCH and BatchID <= :QUERY_PARAM_CURRENT_BATCH

on the GD view, any batch that creates or updates a golden record (including overrides made through authoring) will already be picked up and sent - you don't need AuthoringType in the payload to make the trigger work.

If you still want to expose "how this golden value was set" in the payload

If the real requirement is to tell consumers whether the change was an override vs. a new entry, you have an option, since the technical attribute can't be pulled onto GD directly:

Add a custom attribute to the entity (e.g., LastAuthoringType) and populate it via a post-consolidation enricher/rule that copies the value from the relevant SA record(s) into the golden/master record during certification. This is the standard workaround used for other SA/SD-only technical fields (e.g., PublisherID, SourceID) when they need to be surfaced at golden level.

This approach lets you keep your Named Query at GD view type while still surfacing authoring-type information in the notification payload.

Thanks and Best regards,
Haashim

Login to post a comment
More topics in xDM - Integration
See all 87 topics
Help Desk Software by Freshdesk