Dynamics Community Forum Thread Details

There are development machines topologies, where you may host several AOS instances for development purposes, working with several MicrosoftDynamicsAX Databases. Let’s take a look at couple of AOS instances in Dynamics AX Server Configuration Utility

The one above is default AOS installation, where TCP/IP port is 2712 and WSDL port 8101
Another instance is the second one installed:

Here the ports are increased by 1: TCP/IP 2713 and WSDL 8102 respectively
Let’s assume that as AX X++ developer you are using this second instance with ports 2713 and 8102
You create in Visual Studio 2013 SSRS report.
In AOT you have already created report data provider class
Now in visual studio you create report project and add dataset (Dataset1 on picture below)

Let’s now give it data provider class:

You change Data Source Type to Report Data Provider and in Query click on selection button

In the selection list you can’t find you data provider class.
If in Visual Studio you open AOT and expand classes – it is there. The class is present in VS Application Object Tree classes section
Where is your class?
Let’s try to open AX 2012 with AOS default instance, see picture on the top, where ports are TCP/IP port is 2712 and WSDL port 8101. Recreate you report data provider class in this environment, then open Visual Studio, create AOT object. Close Visual Studio. From AX AOT Visual Studio Project right click and Edit your just created report project. At this point in your dataset switch Data Source Type to Report Data Provider and open selection of data provider classes. You class should be in the list
It seems that Visual Studio when selecting DP is talking to AOS server(s) via default port, likely WSDL port 8101
Please, note that in the example, where problem exists AX AOT and VS are trying to talk through different WSDL ports (8102 and 8101)
So the natural way to fix hidden class issue have both AOS and Visual Studio talk via the same ports. This is by default happens with first installed instance of Application Object Server. If you have your own dedicated AX 2012 developer machine you likely never have the problem and situation described in this article
If you share several installation of AX with separate databases and AOS server, then you may find yourself in this situation. And it is not necessary limited to described scenario where SSRS report data provider class is not present in the selection list
Author, Andrew Karasev, is X++ developer and Dynamics AX 2012, 2009 and Dynamics 365 Finance and Operations techno functional consultant

No record found.