I think that most of you who are writing applications connecting to Dynamics 365 already wrote thousands of some similar code: It’s simply connecting to Dynamics 365 using connection string and querying contacts. Connection string looks like that:
If you are following the latest news regarding Dynamics 365 ecosystem, you are probably aware of the fact that Microsoft decided to put everything upside down, change the naming of every technology and use the old names with some new things. Of course I’m exaggerating a little here, but some changes are really crucial and […]
Defining required and optional fields are always an important part of every Dynamics 365 project that I have ever worked on. Have you ever thought properly about the server-side validation on that matter? From my experience, Dynamics CRM Customizers/Developers usually just create fields with proper value in “Field requirement” field. I hope that everyone […]
I believe that if you have ever written a CRM plugin, you are aware of the event execution pipeline (https://msdn.microsoft.com/en-us/library/gg327941.aspx) and that the operation is run in transaction which means that if there will be any exception, the whole transaction will be rolled back. Pre-operation plugins and Post-Operation plugins are also run in transaction, so […]
Recently I was caught up in the discussion about early bound entities and late bound entities. One of the argument of the “late bound supporters” was the fact, that using late-bound allows reusing the same plugin for multiple entities (so for example create a plugin that runs for all activities or a common plugin for leads/opportunities/accounts). […]