Hi @RogerS , This macro is pretty neat. Can you help us understand a use case for this macro? As I understand it is not for security reasons that the data is masked, because it can be decrypted, or is the double MD5hashing after a find replace tool sufficient to secure the original content?
@RWvanLeeuwen I'm going to take a guess that the use case is that PII data should be masked, however the data requires that the variables still be made available.The replacement of characters and the double MD5hashing is meant as a security feature.
Pretty straight-forward. Drop the MACRO into your workflow, select the fields you want to mask, then add a select tool and deselect the unmasked data. EASY! Thank you.