Last time I tried to create a new systemuser, which is mananged in an other domain as the CRM system, I wasn’t able ton enter a backslash key in the domain name field.
After some investigation, it turned out that I was not able to enter \ in any field. I’ve reproduced this issue on multiple systems (On-Line and On-Premise) and multiple language packs.
With help of @nzregs I could verify that it is not a general problem. After comparing system parameters, I found out that I was able to enter a backslash with an different keyboard layout than ‘de-de’. Therefore I opened a ticket with the CRM support which is currently under investigation. It looks like it is a bug in the default form scripts.
If you have to enter a backslash in the meantime and you are experiencing the described problem, you could either copy/paste it from anywhere or you could enter ALT + 92.
This issue was confirmed as a bug. The fix will be released with Rollup 7, which is currently scheduled for March 2012.
In a recent project I had to develop a plugin which is executed in the plugin sandbox. The sandbox restricts the rights plugins to a ‘safe’ amount. See http://msdn.microsoft.com/en-us/library/gg334752.aspx for a description. According to the SDK, web request are allowed.
Part of my task was to send a request to a web service which expects data URL-encoded. Normally you would use following class (part of
HttpUtility.UrlEncode("some data here");
I was surprised that this leads to a
SecurityException if used in a sand-boxed plugin. The sandbox does not allow the use of this class.
Instead of rewriting the method (I hate reinventing the wheel…) I’ve searched for a replacement, and found
Uri.EscapeDataString("some data here");
which is usable in sand-boxed plugins. For my task the result was the same as with
UrlEncode, however I am not sure I they are different in their results.
One important thing that is often forgotten during/after the installation of Dynamics CRM is to properly set the SPNs for your service accounts (if necessary 😉 ).
Here are three links which I often take as reference when we plan new deployments: