AIF Web service error

AIF that hosted in web service sometimes cause an error that very hard to trace, below is one of the error generated when we accessing the AIF webservice.

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

After a long time search also enable the debugging, I found that the NameSpace in the services is not properly update. So if you guys encounter this error please make sure the NameSpace define in AX is the same with the NameSpace that been generated in the web services.

Sample:
-<wsdl:operation name="find">
<soap:operation style="document" soapAction="http://schemas.microsoft.com/dynamics/2008/01/services/SalesOrder/find"/>

The bold character is the namespace, make sure that its the same with the name space in the AX services object.

Note: this is only one of the possibilities for the respective error message.

Inventory master data migration AX 2012

Sometimes using DMF is quite hard if you don't know how to configure and use it, below is the sample code how to do the inventory master from code (not product master).
Actually we can always use standard AX 2012 code to release the product master but we need to configure it again once it's become the inventory master; so below code can help to release the inventory master with pre-configured data that you can define from a CSV file.
We will use help from AIF class InventItemService.
    

Customer account number sequence AIF error

Recently I'm facing an error regarding inserting a record from AIF (AX 2012), below are the message:

• Line=1, Pos=1256, Xpath=/Customer/CustTable[1]/DirParty[1]
• The number sequence Acco_368 does not allow the Customer account to be defined.

To resolve this issue is to change the customer account number sequence as a manual.