The information in this post is based on Dynamics AX 2012 R3. It may or may not be valid for other versions.
When asked to add a new field, change some logic or do some other modification to a document service running on an AIF integration port (inbound or outbound), I often end up spending way too much time searching for the actual classes behind the service.
Sure, most of the elements from the standard application are named fairly consistently, but way too often, custom code is not. The forms for setting up document services in AIF does not provide an easy way to see what code actually handles a service, but knowing the name of the service itself (which you can easily find in the port configuration), you can run this small job to save yourself some time – here it’s running for the CustCustomerService, but you can change that to whichever service you need:
static void AIFServiceCheck(Args _args) { AxdWizardParameters param; ; param = AifServiceClassGenerator::getServiceParameters( classStr(CustCustomerService)); info(strFmt("Service class: %1", param.parmAifServiceClassName())); info(strFmt("Entity class: %1", param.parmAifEntityClassName())); info(strFmt("Document class: %1", param.parmName())); info(strFmt("Query: %1", param.parmQueryName())); }