Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
while across the inbound services in ax 2012 r3, found a little bit confusing error and here the details,
Create one inbound service with an operation which accept one parameter as well. This is worked fine. The details below,
Visual Studio side with exposing the param.
Param shows with in the service reference.
Then i created another method in data-contract class and added into operations & deployed.(CIL & Full CIL done.) First method parameter type change immediately after service reference updation & shows the invalid parm type error. Here is the second method details,
First method param error after service reference updated.
Reference of the 1st method after service reference updation.
I don't know why this happen when i add the 2nd method cause the first method param type. The error cleared after i either remove the 2nd method param or totally removed the 2nd service operation. Any help may appreciated.
The error says that you have two definitions of 'customer' object - one in ConsumeExternalWebServiceTest.ConsumeExternalWebServiceRef namespace and the other in ConsumeAxserviceWFA.AxServiceRef namespace. And you're trying to assign an object of one type to a variable of another incompatible type, which isn't supported.
It seems that your AX service refers to a proxy class generated for another AX service. Why? It sounds very strange; maybe you did the whole architecture wrong by mistake. If it's your intention, can you please describe your business scenario?
Also, the first picture shows that you're using AifCollectionTypeAttribute while the method doesn't return any collection at all. It returns a single integer. Therefore you should delete the attribute.
Dear Martin Dráb,
Am really sorry to late response.
Point 1: I understood that error. The 'customer' object definition changed only after the 2nd service operation 'parmDataset' has been deployed. Otherwise it works fine. Thats am surprised.
If you noticed anything unexpectedly please guide me.
Point 2: It occurs while am testing some service methods. Obviously not an intention.
Point 3 : Ofcourse. Unexpectedly put the integer as collection type. Will be no more.
If you didn't want to use a proxy inside your service operation, then remove these things from your code. Fixing the logic will also fix the compilation error (maybe you'll get another one, but that's a different story).
Right, nonetheless just eager to know whats happened there. Thank you.
Business Applications communities