Guidance on Exporting identityMap: Email with SHA256 to AWS S3 | Community
Skip to main content
Y
yesraptors12
Level 2
April 9, 2024
Solved

Guidance on Exporting identityMap: Email with SHA256 to AWS S3

  • April 9, 2024
  • 1 reply
  • 829 views

Hello Adobe RTCDP Community,

 

I'm currently working on a project where I need to export the `identityMap: Email` data from Adobe RTCDP, applying a SHA256 hashing function, and then store the resulting dataset on AWS S3. I did try using the calculate function but without lucks.

Could anyone provide insights on how to implement this process within the Adobe RTCDP platform?

 

Regards,

Rap

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 derekselby

I agree with Bryan. Right now the calculated fields for destination does not support complex arrays, only simple arrays like an array of ints, strings, etc... Documentation for that can be found here: https://experienceleague.adobe.com/en/docs/experience-platform/destinations/ui/activate/export-arrays-calculated-fields#how-to-export-calculated-fields

 

Your best option right now is to SHA256 hash the data in the dataflow as it comes in or if that is not an option, use Data Distiller to extract the email values, hash, then store back in a dataset.

1 reply

brekrut
Adobe Employee
brekrutAdobe Employee
Adobe Employee
April 9, 2024

Is there an option to hash the data before it is ingested into the CDP or use dataPrep functions to hash the email address?

 

This may be a better option to hash the data instead of hashing the data on the way out.

derekselby
derekselbyAccepted solution
Level 2
April 9, 2024

I agree with Bryan. Right now the calculated fields for destination does not support complex arrays, only simple arrays like an array of ints, strings, etc... Documentation for that can be found here: https://experienceleague.adobe.com/en/docs/experience-platform/destinations/ui/activate/export-arrays-calculated-fields#how-to-export-calculated-fields

 

Your best option right now is to SHA256 hash the data in the dataflow as it comes in or if that is not an option, use Data Distiller to extract the email values, hash, then store back in a dataset.

Terms & ConditionsAccessibility statement

Loading footer...