Q1

When I use a Delete operation in the Dynamics AX 2012 connector to delete multiple customers, only one customer is deleted. What should I do?

A1

This happens when a record is mapped to a KeyField element. During the mapping stage, when working with Read, Update, and Delete operations, you should use the EntityKey element and not the KeyField element if you want to submit multiple record requests in a single execution. For a single record, you can use either the KeyField record or the EntityKey record.

Q2

When I use an Update operation in the Dynamics AX 2012 connector to map a RecID element, the operation fails. What should I do?

A2

To prevent this from happening, you should change the RecID's picture size from 9 to 12.

Q3

Why am I getting the “The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element” error?

A3

When a Dynamics AX 2012 connector uses a Find or Read operation for more than 15 customers (Customer Service) the Activity Log\C.Sys.ErrorDescription variable shows the following error:

Error 1251: Dynamics AX call error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.

System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element

When working with a Dynamics AX 2012 connector on machines running .NET Framework 3.5 or 4.0, the maxBufferSize and maxReceivedMessageSize parameters appear in the client.config file under the <binding name> tag. To prevent this error from occurring, the maxBufferSize and maxReceivedMessageSize properties should set to higher values.

When working with a Dynamics AX 2012 connector on machines running .NET Framework 4.5, the client.config file does not have these parameters, so you need to set them manually.

Note: Changes to the client.config file's parameters take effect immediately The Magic xpi project does not need to be restarted for it to use the new value.

Q4

Why am I getting the “System.TimeoutException: This request operation sent to net.tcp://ax2012r2a:8201/DynamicsAx/Services/TestCustomer did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout.” error?

Note: net.tcp://ax2012r2a:8201/DynamicsAx/Services/TestCustomer is only an example. This issue can occur with any WSDL URI.

A4

When a Delete operation is performed for more than 300 records, the System.TimeoutException error appears in the Activity Log\C.Sys.ErrorDescription variable.

System.TimeoutException means that the request operation sent to net.tcp://ax2012r2a:8201/DynamicsAx/Services/TestCustomer did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout.

After 5 to 10 minutes, the deleted customers (or any other element that you tried to delete), are deleted from the Dynamics AX server. No rollback for this error takes place.

This is happens when the client.config file contains the following values: closeTimeout="00:05:00" openTimeout="00:05:00" receiveTimeout="00:05:00" sendTimeout="00:05:00".

To avoid getting this error, the receiveTimeout parameter should be increased manually as the number of records increases.