My colleague Daniel Westerblom at WM-Data asked my a question concerning the fake lookups that I have referenced bellow and that I know are commonly used by many partners. The question was if these customizations are supported.
When I was at convergence I asked this explicit question to, I think it was, Clint Warriner (CRM Escalation Engineer at Microsoft Support) and he gave me confirmation on what I had suspected, that these customizations are not supported. They fall under the last point concerning unsupported customizations described in the SDK: “The use of custom HttpModules to inject HTML/DHTML into the Microsoft CRM Forms.”
Since the HTML DOM is modified, this is not supported.
The reason for this is most probably that Microsoft might choose to change this in future releases of CRM (for instance CRM 4.0) and might also have internal scripting references to objects they expect to be there according to the standard HTML DOM.
I don’t know if these fake lookups will upgrade from CRM 3.0 to 4.0 without problems. If you have any experience of it, please let me know.
If you have any comments on this subject, please feel free to comment bellow. I always publish comments that concern the subject and are not directly offensive. (I have activeted moderation on comments just to avoid comment spamming).
Gustaf Westerlund Microsoft Dynamics CRM Consultant
Usually I develop on a CRM server but sometimes, when a larger piece of CRM-independent part needs to be developed, I develop on my local machine.
Presently I am working in an integration project with an integration engine and needed to consume one of it’s webservices. I did so and I added some code to handle it (intellisense working fine) but when I tried to run it, it crashed on the constructor or the service class with the following error:
System.IO.FileNotFoundException: File or assembly name gvy6umsk.dll, or one of its dependencies, was not found.
There was also a reference to the WindowsTemp-directory. The filename is obviously some temporary filename for the proxy-object.
After checking the web a bit, I found the error to be caused by the fact that the user running the software, did not have read/write access to the c:windowstemp directory. I fixed it and the program ran like it should!
So, if you are in the same situation, just fix the right for the windowstemp directory and you should be fine.
Gustaf Westerlund Microsoft Dynamics CRM Consultant
Michael Höhne of Germany is a very resourceful CRM MVP and has just published a great posting on how to, in a simple and good manner create include files for javascript in a supported way. So, with great applause from me and hopefully the rest of the CRM community, give it up for Michael! Here is the link:
http://www.stunnware.com/crm2/topic.aspx?id=JS18
Gustaf Westerlund Microsoft Dynamics CRM Consultant
Integrating with map services like Microsoft Virtual Earth, Google Maps can bring your CRM or SharePoint application great increases in features at a relativly low cost. Microsoft uses Microsoft Virtual Earth internally and the Microsoft SharePoint Products and Technologies Team Blog has written an interesting posting about this which includes a reference to a codeplex project including all code for the internal project.
I havn’t checked it out, and it is used for SharePoint in the example but I believe that a lot of the code probably can be used to develop a Virtual Earth driven map service in Microsoft CRM.
So, without further ado, please read the posting and check out the codeplex project if you are interested!
Recent Comments