[URGENT] Incorrect 'Crypto Extension' with md5 on Extensions tab

[natpatch_p_]

I faced a problem when using 'Crypto Extension' to hash my custom Data Source with md5 method on Extensions tab. The problem is the hashed value will always be â d41d8cd98f00b204e9800998ecf8427eâ even the exact value before hashing is changed. How could I use this function correctly?

[brian_kranson]

Natpatch Here is a link to more information on the Crypto extension. https://community.tealiumiq.com/t5/Tealium-iQ/Crypto-Extension/ta-p/13596 The Crypto Extension will MD5 hash a UDO datasource and then overwrite that datasource with the new MD5 hash value. My guess is that if you are always getting the same MD5 hash value is that your UDO datasource always passes the same value to the MD5 hash algorithm. An easy way to test this is to add a javascript extension right before the MD5 hash to log the value of the datasource you are trying to use. Then add another javascript extension right after the MD5 hash extension to show the new MD5 hash value of the datasource. Once you are done with your testing, you will want to remove these two extensions. See screenshot below.

[adrian_browning]

Brian not as simple as that I'm afraid. Am talking to the customer directly at present.

[brian_kranson]

Adrian, After you have more information, please ping me so we can get accurate information to the community at large. Thanks for the support.

[adrian_browning · Accepted solution]

ANWSER: The crypto extension does not support numeric values being passed in and converted. You need to make sure that the value being converted is a string representation.

[natpatch_p_]

Brian and adrian, Thank you for your fast response. I have followed Adrian's answer to convert to string before using crypto extension. It's work now!