Dynamics CRM: On-demand or on-premises? Consider your reporting requirements
Companies willing to implement Dynamics CRM 2011 must decide whether to deploy it in their own infrastructure (on-premises) or to
Microsoft Dynamics CRM (Customer Relationship Management) was an application that helps businesses manage sales, marketing, and customer service processes. It has been replaced by Microsoft Dynamics 365. [Wikipedia].
Companies willing to implement Dynamics CRM 2011 must decide whether to deploy it in their own infrastructure (on-premises) or to
Earlier this year, I bumped into an odd behaviour in Dynamics CRM 2011, which has been recently confirmed by Microsoft
Not sure if I should be happy about it, but a couple of months ago I discovered my first bug
Address data deserves better than chaos. Precision, consistency, and global standards aren’t luxuries—they’re necessities. ISO 3166?1 brings order where systems often stumble.
Understanding how business units define hierarchy and control access in Dynamics CRM is key to avoiding permission pitfalls. When structure shifts, so do security boundaries—often with unintended consequences.
There’s something infuriating about a system quietly excluding the records you most need to see. Digging into the logic behind Dynamics CRM’s filtered views reveals not just quirks, but assumptions baked deep into its bones. The kind of thing you only notice when the data just doesn’t feel right.
Automated record naming in Dynamics CRM using JavaScript—generate structured, human-readable names for records based on owner and other fields, while locking its Name to enforce consistency.