Skip to Content
0

SetVariableExt - Behavior

Aug 25, 2017 at 10:31 PM

76

avatar image

Hi Folks,

I have used SetVariableExt many times before, however i'm not able to re-collect my thoughts of below behavior.

Scenario

1 query with variable (ZDATE)

  • DS_1
  • DS_2 (Duplicate of DS_1)

When i pass the script as "Application.setVariableExt("ZDATE", "value"), this will pass value to both the data-source or any other data-source within the application with that Variable name. (this is good)

Now when i pass or target DS_1.setVariableExt("ZDATE", "value"). In this case my expectation is that only DS_1 must be triggered with passed value and NOT DS_2 right?.

If Yes, than its not the case in my scenario. If No, then i believe this is because of same variable in both queries. I even tried creating another query with same variable but the result was same. DS_1.SetVariable affected both data-source. Then i created new variable for DATE in second query and that worked because of obvious reasons.

I believe design studio can handle multiple 'dialog-box' when we use SetVariableExt ?

Appreciate your response

**Also i see TAG has been updated to "SAP Lumira, Design edition" Is there anything can be done to alert community on this? For last 2 days i tagged to "SAP Business Design Studio". Will be helpful to others, or perhaps i miss something.

Regards,

Fahad

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Mustafa Bensan Aug 28, 2017 at 08:26 AM
2

Hi Fahad,

Regarding "Now when i pass or target DS_1.setVariableExt("ZDATE", "value"). In this case my expectation is that only DS_1 must be triggered with passed value and NOT DS_2 right?.", have you checked that the Merge Prompts property of the application is set to false ?

Mustafa.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Perfect Mustafa.

That served as my memory Jump-Start.

0