A while back, I posted some articles which used the Support Debugging Tool and non-logging Automatic Debugger Mode triggers to "encrypt" data.
The use of the word "encrypt" was unwise as it has connotations about providing a level of security and possible compliance with various standards.
So, to more accurately describe what is happening AND to ensure there is no confusion about exactly what the example code is doing, the posts have been updated to refer to "obscuring" the data.
If you have deployed the code at any sites, please do the following:
Here are the links to the updated posts:
Note: The function used for this example ito obscure the data is a very simple algorithm built into Dexterity and is only meant to stop the data from being easily readable. It is NOT secure and does not meet any compliance standards for encryption of personal data. Use at your risk.
If you want proper encryption of Credit Card details, there are solutions from Independent Software Vendors (ISVs) for Microsoft Dynamics GP.
For details on ISV solutions, go to http://pinpoint.microsoft.com/en-US/home, on the right click on applications, then search for “Microsoft Dynamics GP Credit Card Encryption”.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.