Accessing Event Variables in ACS (Transactional Messaging) | Community
Skip to main content
davidh2892249
davidh2892249
New Participant
July 13, 2020
Solved

Accessing Event Variables in ACS (Transactional Messaging)

  • July 13, 2020
  • 1 reply
  • 2463 views

Hi there,

 

I'm setting up some Transactional messages whereby the email trigger must be real time, but I cannot guarantee the profile will exist in the ACS profiles table.

Therefore I am setting up as an event transactional message rather than a profile transactional message.

 

At a later date, I'd like to be able to access details of each record of the event for follow up processing. This could be:

* Exporting back to data warehouse

* Updating a custom resource in ACS

* Cross referencing with profile data

 

For any of these activities, I need to be able to query the event and access the custom fields (and their values) that were created for the event. However, when i use a workflow query and change the resource to one of the events that has been set up... only the standard attributes (e.g. status) are visible, not the custom ones created for the event.

 

Can anyone share any insight on this? Is there a way to access those event fields? (they must be stored as i'm still able to view a mirror version of each email sent).

 

Thanks

 

David 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by bisswang

True, they are not accessible in a query/enrichment activity.

Though they can be used in an Export File activity.

 

Either to upload them somewhere or you could directly parse the same file again in the workflow and then have the values accessible

1 reply

B
bisswangAccepted solution
Employee
July 13, 2020

True, they are not accessible in a query/enrichment activity.

Though they can be used in an Export File activity.

 

Either to upload them somewhere or you could directly parse the same file again in the workflow and then have the values accessible

davidh2892249
davidh2892249Author
New Participant
July 22, 2020

Hi @bisswang

 

Thanks for the answer, really useful to see the ctx data available for export.

 

Are you essentially saying a workflow something like:

Query (delivery logs of event) --> Data Extract (including ctx fields) --> File Transfer (upload) to SFTP --> File Transfer (download) from SFTP --> Data Loading --> I'd now have the CTX data in a workflow temp schema for further processing.

 

And one more question if you don't mind....
Is it possible to query all delivery logs of all events (and then export a common ctx field?)

I think in my use case i'd like to export all delivery logs of all events (without having to specifically query explicit events) and a common ctx field they should all most likely have (e.g. ctx.customerID).

 

I hope that makes sense.

 

Thanks for the help.

Terms & ConditionsAccessibility statement

Loading footer...