cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple entry option in Input parameters of Graphical, SQL View option in data builder data sphere

josephreddy2021
Explorer
0 Kudos
176

Hi All,

I am trying to create multiple entry Input parameters in Graphical, SQL View option in data builder data sphere on Table. I don't see multi entry option for input parameters. Do we have any alternate way to pass multiple values through input parameters of Graphical, SQL View ? EX: Company code , i want to pass CC100, CC200 to the where clause of table/map it to the Company code field.

I appreciate all your inputs.  Thanks.

 

Regards,

Joe

View Entire Topic
Martin_Kuma
Active Participant
0 Kudos

Hi Joe, 

I always use Analytic Model Filter Variable

Martin_Kuma_0-1728028737083.png

 

Directly in view you cannot create a variable. Or at least I do not as it makes no sense as the system will fetch all the data, regardless of the selection. Variables work only in DSP, not for fetching the data from source system - as far as I know 🙂

 

Cheers

Martin

josephreddy2021
Explorer
0 Kudos

Hi Martin,

Thanks for reply. I Used this filters option in analytical model works fine.(Here there was no option to point the variable to Master data objects to show key and text search help to user).

I wanted to use Input parameters to pass multiple values into my SQL Code where clause, to address some complex logic and improve performance, like we do in native HANA Table functions (Here in graphical/SQL view input parameters can be created referring to Master data objects to show key and text search help to user, same option is not there in analytical model filter variable.

 

Thanks,

Joe

Martin_Kuma
Active Participant
0 Kudos

Hi Joe, 

I get it now. You want to use multiple-values in the model/story, but pass it to the view. The view allow single value parameter only, you can use the SQL IN, but still you have to create a parameter for each value and you do not know how many values the user enters. This is not in. Yet :). Even python will process only loaded data. Fetching is affected only with the parameter in the view. That is why the best approach is to persist the data (disk only), instead of federating it and then use the multi-value variable. 

Regarding the text / F4 like help. I add a text assoc to the field and create the variable on top of the text assoc field (description), not the field (key self). You need to restrict the view with language (if you use multi-lang). Can do with a view parameter :). 

Cheers,

Martin