Sap Analysis Office the Document Is Reloaded Again
You might have faced the need to merge/blend multiple HANA/BW information sources to build applications, but this is non explicitly achievable in stand-solitary SAP Lumira Designer. Interoperability between Lumira Discovery, Lumira Designer (Composites), and Rich data source combination features in Lumira Discovery allow us to use merged/composite datasets from multiple sources in SAP Lumira Designer.
Although this has been available since SAP Lumira 2.0, the simply catch was that any update to the data source will non become reflected in the SAP Lumira Designer application unless a manual refresh of the SAP Lumira Discovery storyboard or scheduling was done.
With the introduction of SAP Lumira Designer 2.ii, SAP addresses this issue past adding a new component to their list – the "Documents" technical component. This new technical component allows application designers to refresh their Discovery-acquired information sources from SAP BW or SAP HANA using APIs or methods of the technical component. There are other use cases for the Documents technical component, which we will exist looking at in other subsequent blogs, but this i focuses on the data refresh use case only.
Refreshing offline Information Sources
For this blog, we are going to create a very simple application with a elementary enough information source that is acquired from an SAP HANA view. At a later point, we'll add more data or update the HANA View data and so refresh the offline data source using SAP Lumira Designer to come across if the changes are reflected.
As seen beneath, we are first creating a new SAP Lumira Discovery story with information acquired from a HANA Calculation View. Since we're keeping things elementary here, our story simply has a couple of dimensions and one central figure. By principle, the same technique should work regardless of the volume or complexity of the information source used.
Again, we're more interested in using the caused data within SAP Lumira Designer and as a result, we're not also bothered about creating multiple visualizations or even a complete storyboard using SAP Lumira Discovery. Still, in the epitome below, you should be able to see that we're going alee and saving the SAP Lumira Discovery story that we've just created. Nosotros are saving the document locally hither, just the same will work fifty-fifty on the BI platform.
One more than important aspect to note here is that the SAP Lumira Discovery story is saved with all the data, i.e. the Relieve without informationcheckbox is Not checked.
Now, when we head back into SAP Lumira Designer, to see the newly saved SAP Lumira Discovery story, we might have to refresh the documents. This can be done using by right-clicking on the Local Documents folder (or BI Platform Documents folder if you've saved your Discovery story on the platform) and selecting the carte du jour pick Refresh.
One time the Lumira Document is seen in the folder, we're opening the document and creating a new application within the same document by correct-clicking on the document and selecting the choice Create Awarding. We're going with a blank application for our purpose. The moment we do this, we're adding the Documentstechnical component to the awarding.
As role of the next stride, nosotros'll add together the offline data source we acquired using SAP Lumira Discovery to the application. This can be done by right-clicking on the Data Sourcesbinder inside the Outline View of the application and selecting the carte option-Add Offline Data Source…. The information source that nosotros used in the SAP Lumira Discovery story will be displayed and this is selected equally the data source for the application besides.
Notation: The feature of adding an offline data source volition show up merely when the Lumira discovery story has an imported data source. If the story is created on Alive data, the choice will not be displayed.
Once again, since the agenda is to proceed the application simple, we are merely using a Crosstab to consume the added data source and a push component to refresh the information source using the Documents Technical Component.
Now, within the On Clickresult of the button component, we are adding the required API that will allow terminate users to refresh the offline data source from the SAP Lumira Designer application itself. The script for this is pretty uncomplicated:
Document.startDatasetRefresh();
Finally, triggering a dataset refresh will only refresh the information source. It's as well imperative to refresh in society to actually reload the Data Source component to reflect the refreshed data. This tin can be done using the API shown in the screenshot below:
The best place to exercise this would exist the event that is triggered Afterward the dataset has been refreshed, which is the On Dataset Refresh Completeupshot for the DOCUMENTtechnical component.
When the awarding is executed, it will show the information using which the story was created. At present, in our example, we are manually updating the data on the HANA view to check if the dataset refresh works in the SAP Lumira Designer application. Clicking on the refresh component volition kickoff the data refresh and latest data will be loaded to the table component. We've displayed the "Before" and "After screenshots for your reference below:
If the requirement is to see the latest data whenever the application is executed, the same script tin be written on get-go up
***
Equally mentioned earlier, the Documents technical component can exist used for another use case when combined with the Authoring technical component. But in this blog, we have covered the biggest apply instance it has – refreshing datasets acquired in SAP Lumira Discovery. This new feature should accost the concerns that a lot of customers have had with interoperability every bit a characteristic.
Stay tuned to our space for more updates! Learn more well-nigh Visual BI's SAP Lumira Offerings here.
Source: https://visualbi.com/blogs/sap/lumira-2-2/refreshing-acquired-data-sources-sap-lumira-designer-2-2-documents-technical-component/
0 Response to "Sap Analysis Office the Document Is Reloaded Again"
Post a Comment