Spießrutenlaufen is everywhere. Even fundamental actions like creating a new entity in CRM are subject to irreversible hasty choices that we all come to regret later. Introducing CRM Tipsters Illustrated Guide to Entity Creation in Dynamics CRM. Download a full size image or a hi-res PDF version.
Tip #368: Keep your early bound classes lean
The convenience of early bound classes often overshadows the side-effects of using those. It is, indeed, very easy to write: CrmSvcUtil.exe /url:https://myorg.api.crm.dynamics.com/XRMServices/2011/Organization.svc /out:GeneratedCode.cs /username:”myname@live.com” /password:”myp@ssword!” then add generated file to the project and use syntax-checked a.accountname = “Acme Inc” instead of a[“acountname”] = “Acme Inc” (see what I’ve done here to demonstrate the usefulness of […]
Tip #263: Avoid unnecessary plugin execution
Inspired by our rather radical approach to enforcing development discipline, Andre “I’ve got 88 in my handle” Margono decided to pick on another sinful habit in development, this time within plugin development. Corporal punishment triggering behavior this time is to select all attributes as filtering attributes for Update message. Unfortunately, plugin registration tool that comes […]
Tip #230: Ban the browse button
I like German words. Take, for example, Spießrutenlaufen. If you like me, and don’t speak a word of German, you know, just by looking, that the word means business, the word means corporal punishment. I often wonder if ignorance of the developers can be cured by introduction of Spießrutenlaufen for coders. Function is longer than […]