Freigeben über

Phil and Mort...

  • Artikel

I laughed out loud when reading this interview between Phil and Mort on the CRM Team blog. Phil is trying to explain to Mort the differences between supported and un-supported CRM customizations. So it seems I am not the only one having those similar discussions with customers and partners.

To read the interview, go here: https://blogs.msdn.com/crm/archive/2007/04/13/unsupported-scripting.aspx 
Please share your opinion on this interview!

Maybe the comments area would also be a great location to publish some features you would like to see in newer versions of Microsoft CRM.

Comments

  • Anonymous
    April 14, 2007
    The conversation does, in a humorous way, emphasize the issues surrounding unsupported scripting, and of course as a vendor, Microsoft can only take the position given by Phil. However, I think characterizing the interviewee as Mort oversimplifies the variety of thinking among those who are in unsupported territory, and does nothing to address the factors driving unsupported solutions. I doubt that it's a lack of understanding the consequences that makes most developers opt for unsupported choices. When you're up against non-negotiable requirements, you do what you have to do. And it's not always a lack of understanding by the customer either; sometimes the non-negotiability of a requirement is simply a fact of the business at hand. I'm not criticizing the post though. The message is good; it just doesn't change anything. Anyway, the only thing I want in the client-side scripting model is access to every widget on the form through a documented DOM--e.g. not just the objects exposed via crmForm.all. Right now crmForm.all serves a sort of social contract where Microsoft agrees not to change the DOM from that point on down to ensure future compatibility of custom scripting. I would happily give up the promise from Microsoft to never break my custom scripting in exchange for documented access to the whole DOM and a promise to publish any changes to it, thus putting the responsibility of keeping my customizations compatible on me.