Share
Report
99I am currently facing a situation where a company deployed crm 2013, configured SSS Email, and deployed it to certain users to test/use in the field.
One of the users was using the appointments as a notes section for the account, these "notes" were very much inappropriate to say the least. The appointments then went of to the account holders email along with the inapporpriate "notes" and it caused an entire sandstorm... So we disabled email's, built a custom entity called NoteBuilder to store notes about customer accounts, this entity cannot leave CRM. Problem solved for notes for sales guys.
Now since that incident about 6 years ago there has not been any Email functionaility at all, its configured but disabled for all users. We are now on Dynamics 365 v9.0.30.2 On-Premise and since we have expanded and brought in other departments we need to open up communmication between these departments within CRM and encorpate the service module.
Before we enable emails again to test, Is there anyway to check the database or system for old appointments or emails that could potentionally be sent out the moment we enable emails for users? Can we purge those activities/appointments, or remove them from a queue if so?
Just looking for possible solutions for damage control before we enable emails again.
All responses (
Answers (
