Unsupported Scripting

Phil and Mort...

A Freaky Microsoft Dynamics CRM Blog — Sat, 14 Apr 2007 04:58:04 GMT

I laughed out loud when reading this interview between Phil and Mort on the CRM Team blog . Phil is trying

re: Unsupported Scripting

Pete — Tue, 17 Apr 2007 05:07:56 GMT

Best blog yet, It Philip did a great job getting the message across while being funny.. From personal experience I can say, give it some thought before getting excited about all the unsupported opportunities available :)

re: Unsupported Scripting

Miklos Hollender — Wed, 03 Sep 2008 18:13:56 GMT

OK, but you should submit them on a non-official blog then, or something.

You Microsoft guys really don't understand something: the customizer isn't the user. The customizer is the reseller. So the customer goes like I bought this program from you and it doesn't do X and Y and I am really disappointed because I think every CRM software should do X and Y. So fix it. Now. No ifs, no buts, fix it. That's what resellers have to do. Which means resellers need to do unsupported stuff. Not because they want to, but because they are forced to.

re: Unsupported Scripting

Simple Simon — Fri, 12 Sep 2008 23:21:11 GMT

Miklos has nailed it for sure, but I also understand the MS position (having been-there-done-that all the way back to the '70s IBM mainframes).

P.S. I'm reading this blog preciseely because of the "So fix it. Now. No ifs, no buts, fix it." attitude that I am dealing with right now!

re: Unsupported Scripting

Dave Schinkel — Tue, 23 Sep 2008 21:02:47 GMT

>>>Because I want customers to have a great ‘overall’ experience with our product. If that means missing out on some instant gratification for a better experience over the entire product lifecycle then so be it.

The overall moral of the story is:

1) you just bought a canned system that you are reliant on Microsoft providing the "functionality". The concept of this system being extendable in any "normal way" such as using standard .NET, JavaScript, or even CSS is "unsupported".

So the conclusion is, custom code it with ORM, design patterns, etc. and you can do "what you want" and create "what you need" for the business as a whole.