Optional Filter Variable appears as Mandatory in OData Service of an Analytical Model

[maffio]

Hello expert.

I have an Analytical Model in Datasphere, which has, among other things, two standard filter variables: one is set as Mandatory, the other one is not set as mandatory, so that it is optional. Nevertheless, when I try to extract Odata from the Analytical Model, the optional filter variable appears as mandatory, so that I must provide a value, otherwise the Odata Service fails.

Is there a way to treat the variable as non mandatory, even in OData Service?

[KunwarPankajRao]

Hello, I don't have an answer as my analytical models do not have parameters. However, depending on how you are consuming this API, I have a follow-up question. To use the OData V4 consumption API, we need an OAuth client with the purpose 'Interactive Usage', right? But does this mean that a user context must be present in Datasphere itself, or am I mistaken? I am looking for a way to consume analytical model data using cron jobs running in a Kubernetes cluster. So, I’m trying to consume the DSP API as a robot user without any user setup. Is that possible?

[Martin_Kuma]

Seems that for OData all variables are mandatory. Even if not marked as mandatory by the model. 

Try to bypass with changing the variable to dynamic default (using view/dimension). This way the not-mandatory variable will not be needed to be populated with the OData request. 

[Simon_Ye]

It seems only about if you provide a default value for the paramter; if yes, you don't need to explicitly assign a value in your request.