OData function works with one parameter but not two or more

[dcadlereii]

OData function works with one parameter but not two or more

[xuzhg]

@dcadlereii

I can't find a method named "GetProductPrice" defined in the "GetEdmModelV1". Do you mean "GetPrice" method?

So, I can't understand 'https://{{url}}/odata-v1/organizations/GetProductPrice(organizationId='10001', partId='100000-01')', do you mean 'https://{{url}}/odata-v1/organizations/GetPrice(organizationId='10001', partId='100000-01')'

Let's assume that you

1. use "GetPrice" function name
2. has two parameters (organizationId, partId)
3. the action name in the controller is also "GetPrice".

Then, it should work.

"Be noted", your request call has a "whitespace" before "partId='100000-01'. If you remove it, it should work as below Postman snapshot:

Detail test codes, you can find it in daea53c

[dcadlereii]

Sam,

Thanks so much for the quick reply. Your blog is actually what started me on the v8.00 path on this project. The issue was, in fact, the whitespace between the first and second parameter. The function name difference in my posted code example was because I had tried changing the name when troubleshooting while I was creating the original post and didn't realize I had already copy and pasted the old edm model with the modified controller code. I really appreciate your help :)

[RobTF]

I made this mistake as well and it took me a while to understand what was going on; as you say

http://some/path/myFunc(param1='something', param2='another') will 404, whereas
http://some/path/myFunc(param1='something',param2='another') will work.

Another thing to watch out for is that if you get the parameter data types subtlety wrong this can also result in a 404, for example if my parameters to the OData function are Guid and then string, the example below applies;

http://some/path/myFunc(param1='B334999A-CD71-4178-BF55-E66B601C2A45',param2='another') will 404, whereas
http://some/path/myFunc(param1=B334999A-CD71-4178-BF55-E66B601C2A45,param2='another') will work.
(note the single quotes around the Guid param in the first example)

It's technically correct, although I suppose a 400 with details of the typing problem might be more intuitive.

[xuzhg]

@RobTF It sounds we need to support the parameter constraint. So far, i haven't had a design for that.

[xuzhg]

Close it. Please file a new issue if you have questions/concerns. Thanks.