In this short article I am going to explain the Dynamics CRM Event model. It is really important for anyone to understand the basics. Understanding the execution flow of CRM is important because of the flexibility it provides. You might be carried away with it, as it will do anything for you. But it doesn’t mean that you can give everything to your clients. Because it might lead to unnecessary complications like maintenance overheads, performance issues, etc. Following diagram illustrate the concept.
When a request comes through to CRM, everything will fall through the event model. Event model defines how that particular transaction is going to be executed. For instance, assume a user is creating a record, which generates a request to the CRM. When a record is created it has to be committed as part of the database transaction and that is where the platform operation comes into play.
At this point there could be scenarios where you need to do pre and post actions. So with application features like plugins, workflows, etc. you can define pre or post actions that should take place before or after the platform operation
From pre event perspective, you could validate records and stop saving, or you could update existing records before inserting the new one, etc. Post operations facilitates what you want to happen after the main platform operation such as updating related records.
So this event model simply provide you the window to control the transaction against the database.