Topics: |
How to: |
Internet Information Service (IIS) automatically compresses many types of content including script, images, and CSS files to help improve network performance by minimizing the amount of data required to be transferred between the client and the server. MS CRM responses are not compressed by default by IIS. They have the following mimetype:
application/soap+xml;charset=UTF-8
With HTTP compression enabled, you can see up to a 30% reduction in response size. This is shown by analyzing network traffic before and after it is enabled.
Note: Do not enable compression in IIS if you are using an external compression utility.
To enable compression using a command line:
%SYSTEMROOT%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+"dynamicTypes.[mimeType='application/soap+xml; charset=UTF-8',enabled='true']" /commit:apphost
To manually enable compression:
<add mimeType="application/soap+xml; charset=UTF-8? enabled="true" />
To enable compression in IIS using the Configuration Editor:
application/soap+xml; charset=UTF-8
Note: Ensure you test this thoroughly in a test environment before configuring your production environment with this setting.
iWay Application Adapter for Microsoft Dynamics CRM 2011 On-Premises can operate MS CRM with different locales. It also supports special characters such as dollar or euro signs, copyrights, trade mark, and other symbolic characters. To avoid any problems with non-Latin symbols, MS CRM must be configured to use UTF-8 encoding, which is the default setting.
This section lists and describes known runtime issues for the iWay Application Adapter for Microsoft Dynamics CRM 2011 On-Premises.
Entity |
Attribute |
---|---|
importfile |
targetentityname |
columnmapping |
targetattributename |
lookupmapping |
columnmappingid, transformationparametermappingid |
connection |
record1id, record2id |
salesorderdetail |
productid, uomid, productdescription |
quotedetail |
productid, uomid, productdescription |
invoicedetail |
productid, uomid, productdescription |
https://issues.apache.org/jira/browse/XERCESJ-589
Even though this is a very rare case, if it does occur, the error will be logged and an attempt to process a request in the regular way will continue.