Skip to Content


You must be Logged on to comment or reply to a post.

  1. Denica Baeva Post author

     Putting the default value as the column name that is used in the IN condition unfortunately excluded nulls from the result if you skipped the input parameter. Putting the ”’ALL”’ work as a default input parameter but the language has to be SQL not Column Engine. For this option I had to go back to Studio because it wasn’t available in the Web Workbench.

  2. Sudarshan Survepalli

    Good blog Denica. Thanks for sharing it.


    By the way, am right now pondering over an security issue with the construct of the “sample call” you shared – where the filter values are passed openly (unencrypted)! what if the user is was allowed access to TORONTO and then they debug and chage it to LOS ANGELES from the UI code.. is there a simple way to prevent this kind of data tampering?




    1. Denica Baeva Post author

      This is kind of late but if the users have two separate HANA Accounts the quick and dirty way to do it is have a function that returns select current_user from dummy. Have a table that stores the HANA user to city mapping. Join the two to get the current user’s regions and then use those regions as part of an inner join filter in your graphical CV. So then even if they enter LOS ANGELES they wouldn’t get any data.

  3. Oliver Schmidt

    Hi Denica,

    Great Blog and thanks for the Input.

    What ist the reason you use Input parameters for simple filtering problems?
    You state that one of your reason is that you want to ‘ Have filters that get passed down to the base query via input parameters in graphical views.’

    I face a smiliar problem now and tried to find out if the normal odata Filter statement even has this problem.

    Ongoing from this Blogpost i anaylzed the sql statement that was generated by odata by adding “&profile=html” to my odata query.
    I got the generated sql statement and anlyzed it with the PlanViz Tool in Eclipse and saw that the SQL Engine pushes down the Filters to the Tables on it’s own. I even use nested Calculation View and still the where statement is pushed down to the bottom of the execution plan.

    Are my queries not complex enough or are there special queries where the Input Parameter makes a difference for Filtering?


    Oliver Schmidt

  4. Rajaganapathi Rangdale Srinivasa Rao

    Hi Denica,

    I need your guidelines on this approach

    I followed the exact steps mentioned in this blog.  But when trying to display the data through calculation view I’m getting either 0 records (For Option 2 & 3 of “Running CV Alone”) or an error message (for Option 1 of “Running CV Alone”).  I’m currently using HANA 1.0 SPS12

    Also could you please help me in understand the point 3 on the prerequisites for Odata services.

    “Make sure that that the input parameter filter had a default ‘ALL’ value for the drop down”.

    Thanks in advance.





Leave a Reply