Finance | Project Operations, Human Resources, ...

Answered

Service operations parameter error in ax 2012.

(0) Share

Report

Posted on by JAYAKRISHNAN M S

145

Hi members,

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,

Ax side.

ServiceErr1.1.PNG Visual Studio side with exposing the param.

ServiceErr1.2.PNG 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,

Ax side.

ServiceErr2.1.PNG First method param error after service reference updated.

ServiceErr2.2.PNG 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.

I have the same question (0)

All responses (4)

Answers (1)

Martin Dráb 237,904 Most Valuable Professional on at

Like (0)

Report

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.

Was this reply helpful? Yes No
JAYAKRISHNAN M S 145 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,904 Most Valuable Professional on at

Like (0)

Report

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).

Was this reply helpful? Yes No
JAYAKRISHNAN M S 145 on at

Like (0)

Report

Dear Martin Dráb,

Right, nonetheless just eager to know whats happened there. Thank you.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Service operations parameter error in ax 2012.

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Service operations parameter error in ax 2012.

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates