Share
ReportI’m having an issue with service references when deploying changes from one environment to another. I’m not sure if this behavior is expected and for good reason, or if I might be missing something.
The scenario is, we have an bespoke application that consumes web services hosted by an instance of AX (AOS1). Within visual studio, for development, the bespoke application downloads service references from AOS1. The problem can be replicated all from within visual studio, so to keep this simple I’ll describe the problem from a visual studio perspective.
When it comes time to deploy AX service changes from AOS1 to AOS2, all changes from AOS1 are deployed to AOS2 (model deployment), the services are registered and the AIF service port is configured so that the document schemas in both AOS’ are identical.
Within the visual studio project, I change the configuration (not service reference configuration) to point to AOS2. Demonstrated here with code:
Old value:
new EndpointAddress(new Uri("net.tcp://AOS1:8201/DynamicsAx/Services/MyService"))
New value:
new EndpointAddress(new Uri("net.tcp://AOS2:8201/DynamicsAx/Services/MyService"))
When I run my test in visual studio against AOS2 and inspect the response, I can see that it returned a message, with elements (data fields) but they are all null.
I then review the response message in AX (AIF message logging) and can see that the message logged in AX has all the data I am expecting (no null values).
In visual studio, I then update my service reference against AOS2, run my tests and the data is not null, everything works as expected.
I am interested to know why this happens. Currently I am assuming it is related to the deployment (Register) of the services from AX.
Is there something I am missing, is this deployment scenario supported in AX or does anyone have any ideas why this might be happening?
Thanks
Toby
*This post is locked for comments
All responses (
Answers (
294,145
