I'm trying to define a calculation view with an input parameter, in order to restrict selected values in the returning recordset.
After some initial confusion about Input Parameters vs Variables (as in "why does the Variable pop up when I do a data preview, whereas the Input Parameter does not? Would it not be more logical that the latter presented a popup demanding a value? After all, a Variable is just that - a variable...") I am now trying to create an xsodata service for my calculation view.
My XSodata service, however, refuses to activate, because I do not have a "Parameter" in my view. Here's the syntax:
service {
"blabla.blabla.views::CALC_TEST" as "CALC_TEST"
keys generate local "ID"
parameters via entity;
}
And the error message:
[40136] No parameters found for object "blabla..."
The funny thing is that this message appears regardless of whether I have defined a Variable, an Input parameter, or both in my calculation view. And, as previously stated, I'm kinda sceptical about those "Input Parameters", because even though I base them on a column in my view, they don't show up to permit me to do value restrictions when doing a data preview. Only the variables do.
(Maybe the Input Parameters are scared of daylight. I'll try again after dark...)
Has anyone done this before? The idea is (of course) to then use the parameter (or input parameter, or variable, or whatever) to restrict the values received by the OData service.
Regards,
Trond