In this blog I will walk you through on how to swap between connections on run time and in what ways it is more helpful. In this application, I have used two different data sources each with a different connection, one with a BW connection mapped to the Expenses based on region chart and the other one with a HANA connection linked to Expenses trend chart.

Untitled 1.jpg

As you can see, I have provided same selections for both the charts in this application. Though both the charts are using data sources from completely different platforms, having common selection is possible because of using similar info providers in both the cases. To have this convenience you need to load your info provider in both the connections. This cannot be made possible when you load info providers on your data sources that do not have any common dimensions.

Untitled 2.jpg

Even having used two different connections for the data sources, the application loads smoothly and it works without crashing.  This method can be put to good use in places where you need to use very heavy info providers where it can be processed very quickly.

Untitled 3.jpg

In another application, I have swapped between both the connections on a single chart component. Initially the HANA connection is assigned to the data source that is mapped to the chart component.

Untitled 4.jpg

The data source connection changes from HANA to BW on the event of click a button by scripting.In the startup, though the initial view of the data source is edited to display only the required rows and columns, it becomes necessary to edit the initial view every time when we change the connection of the data source.

Since the HANA connection is only active initially, the script for changing the rows and columns on the data source in BW must be entered manually. And also for selection to affect the data source on toggling, a filter must be set to get the selected value on each time the data source connection is modified.

Untitled 6.jpg

The connection is faster and the results are fetched in a jiffy when the HANA connection is active. This functionality comes in very handy when a large data source is accessed and the BW connection becomes relatively very slow, where HANA can be used for swift execution of the application.

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply