General Known Issues

ColumnSet may not function properly in all cases. Microsoft Dynamics CRM 2011 can return fields that are not specified in the request. This is most likely to occur in the following cases:

For activity entities columns to, from, cc, and bcc are returned even if they are not enumerated in the list of requested columns.
For all entities, transactioncurrencyid is returned when any field of Money type is requested.

Certain fields that are indicated as optional according to the metadata are required by Microsoft Dynamics CRM 2011. The following table provides a list of these fields.

Entity	Attribute
importfile	targetentityname
columnmapping	targetattributename targetentityname
lookupmapping	columnmappingid transformationparametermappingid
connection	record1id record2id
salesorderdetail	productid uomid productdescription
quotedetail	productid uomid productdescription
invoicedetail	productid uomid productdescription

Some fields are declared as required, but Microsoft Dynamics CRM 2011 processes messages successfully even when the fields are not populated. The following table provides a list of these fields.

Entity	Attribute
email	messageiddupcheck

Compound operations are not executed in transactions, so it is possible that some records will be created, while the remaining records will not. The result of the executed request will be Fail.

For improved readability, the schemas for RetrieveMultiple requests were generated manually. As a result, the schema structures are slightly different from the MSDN definition. The root query type is QueryExpression, but according to MSDN (and the MS CRM SDK), the root query type is an abstract type QueryBase. The current implementation is used because all other query types can be represented by it.

The following operators that are available as conditions in RetrieveMultiple requests are not supported by Microsoft Dynamics CRM 2011:

Contains
DoesNotContain
NotOn

They are eliminated from the schema.

A workflow, which also contains executions of child workflows, returns a response that contains entity details that are updated according to the primary workflow only. The adapter cannot return entity details, which are affected by a child workflow. This is the case because the workflow log of the primary workflow contains only the GUID of the child workflow, without additional information that is required to retrieve the workflow log for the child entity.

For SearchByBody, SearchByTitle, and SearchByKeywords (Article entity) operations, the rollup element QueryExpression (Query for Rollup operation) must be of type QueryExpression only. It is used for filtering attributes by only specifying the ColumnSet element.

For all advanced operations, the Value element under the OptionSetValue complex type must be set as required. It is currently set as optional in the schemas because of Microsoft Dynamics CRM 2011.

For invoice.SetRelated and invoice.RemoveRelated operations, the EntityReference element must have minOccurs=2 and maxOccurs=2. These are the only settings that will execute the invoice.SetRelated and invoice.RemoveRelated operations successfully.

The Principal element under the PrincipalAccess complex type must be set as required. It is currently set as optional in the schemas because of Microsoft Dynamics CRM 2011.

Distinct does not work in Rollup operations for Order entities.

Formatted values that contain currency symbols may also contain broken characters. This is a Microsoft Dynamics CRM 2011 issue as it inserts redundant bytes. This was checked in Microsoft Dynamics CRM 2011 traces where broken characters were also present. This can be resolved if you know the specified byte sequence being used by Microsoft Dynamics CRM 2011 for separating the currency sign and value.

As a workaround, use UTF-8 encoding (default for Microsoft Dynamics CRM 2011) for XML request documents. In this case, UTF-8 encoded responses with valid formatted values will be produced.

All of the parameters for Advanced operations are declared as optional in the XML schemas. However, some parameters may be required and Microsoft Dynamics CRM 2011 will not perform the requested Advanced operation if these parameters are not defined. Since the MS CRM SDK does not provide information about required fields, it is currently not possible to set proper minOccurs attribute values in the schemas.

When Organization is disabled, Microsoft Dynamics CRM 2011 returns a status code of 200. The adapter does not process this code in any special way.

ColumnSet, Distinct, and Paging Info values in request messages for Bulk Delete operations are not taken into account during processing. Only ConditionExpression and LinkEntities work correctly.

Due to the MSDN definition, the request schema for BulkDelete operations should contain the QuerySet element of abstract type QueryBase for instances of FetchExpression, QueryExpression, or QueryByAttribute. In MS CRM SDK this element is of type QueryExpression. Since the adapter schemas are generated from SDK classes, the same types are being used. All other expressions (FetchExpression and QueryByAttribute) may be represented by QueryExpression.

The validator may fail if a long value is specified for elements that are not of type string (for example, long text in a node that is of type integer). This is the case because of a known issue in the validator implementation that is used in Sun JVM. For more information, see the following website:

https://issues.apache.org/jira/browse/XERCESJ-589

This is rare case, but if it occurs, the error will be logged and the request will proceed with processing.

For CreateException operations, the following exception is generated:

Unable to create exception, SeriesId missing

The SeriesId element is not specified in the MSDN definition or MS CRM SDK, so no changes were applied to the schemas.

If a new user is created in Microsoft Dynamics CRM 2011, but has not yet logged into the Microsoft Dynamics CRM 2011 system (after connecting to a target with the current UI language selected), the target initialization may fail. As a workaround, the user must first log into the Microsoft Dynamics CRM 2011 system and apply the configuration, or have a system administrator set the appropriate UI language ID explicitly. For more information, see Understanding Localization.

Do not use the Refresh option in the context menu for the adapter target in iWay Integration Tools (iIT). The caching mechanism that is used by this option may behave unexpectedly for the adapter target configuration. Use the Disconnect and Connect options for the adapter target instead.