Skip to Content
avatar image
Former Member

SAP DESIGN STUDIO: Triggering an event on Key Press


I am currently trying to find a way to save data input or refresh a page without an onclick event.

I have a Bex Query with exceptions that is displayed in a design studio application. Conditional formatting is enabled and in cases a number input by the user is outside a range, the cell concerned is correctly highlighted in red so that the user can change the value. My issue is that once the user changes to a correct value, he needs to click on a save/refresh button is order for for conditional formatting to reflect the new values. I.e, the cell will be highlighted in red until the user changes the value and then click on save/refresh.

This is quite a normal behavior since i set conditional formatting to true as a start up event.

Ideally would like the conditional formatting to reflect data changes when the user has pressed enter after entering the correct value instead of having to click on a button.

My question is that is there an on key press event that will allow me to call an internal button in the application or do a refresh? Or should I set conditional formatting to true at another place in the application rather than just start up?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Nov 01, 2015 at 08:09 AM

    Hi john ,

    Yeah john through SDK you can achieve key press event .iv'e tried that

    But i guess through native design studio components it is not possible.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello thank you for your feedback.

      unfortunately , I cannot use an SDK at the moment, i tried to find alternatives but in vain.

      So what I have tried so far:

      1. Use on result change event to refresh the query.

              Unfortunately, this is not working since I am getting the following error :

      "Resultset Changed" for data source DS_1 rejected, because this could lead to an execution cycle"

      From what I have searched, this is cause of bex variables. I cannot find a workaround for this.

         2.  I tried adding a Validate button so that even if the user change is not reflected in the conditional formatting dynamically(which would be ideal), he can at least use a validate button that refreshes the conditional formatting part. Unfortunately, the only way this is working is to the save the planning data since it seems the conditional formatting is re-processed only if the planning data is saved. This is of course not ideal since it forces user to save planning data before any validation can be done.

      I need to find a way to re-process the conditional formatting @ button click.

      Can anybody propose how I can do to this?