Skip to Content

SAP Lumira has lot of growing features and more to come. Like any of Lumira release, SAP Lumira 1.28 was also a special release with some of my wishing like Single Sign On with Windows, Support for Hive 0.14 and Promotion Management. So speaking of all that, Data Governance is also one important thing in SAP Lumira which is needed for Enterprise.

One of the feature that customers are looking for is to Save the SAP Lumira Story board as a Template i.e. without data. For WebI users, it’s similar to your “Purge Data” option and for Crystal lovers, it’s like your “Save without Data” on the report. What typically means in that the report is published and shared without any Data so that the Report user has to refresh the Data when he views in order to get new data.


It’s a cool idea and has been proposed here  https://ideas.sap.com/ct/ct_a_view_idea.bix?c=6013C007-A70B-4283-93CE-2531683D816D&idea_id=17E2E1B5-543B-481D-9BB1-A60B7F42EA66https://ideas.sap.com/ct/ct_a_view_idea.bix?c=6013C007-A70B-4283-93CE-2531683D816D&idea_id=17E2E1B5-543B-481D-9BB1-A60B7F42EA66 for voting and we can expect it would come up in some newer versions of Lumira. For those who cannot wait, read on.


It has been sometime since I have posted some Geek Tweaks, so here is one workaround to achieve the same in SAP Lumira. Please note, you are responsible to try it on your own. Be sure to back up your original file in every stage of work. You have been warned!


LUMS the Magic

This small tweak involves manual editing the LUMS file of SAP Lumira after you save it. LUMS file is the default format used by SAP Lumira to save the storyboard, it is also published to the BI Platform when you save it.

Unzip the secret

Your Lumira Document is saved with the extension of “lums” in the folder “SAP Lumira Documents” under the “Documents” folder inside your user profile. Navigate there and look for the Lumira file you saved.

I have made a simple Visualization with SAP BW source which we will try. The process is same for any other data source like SAP HANA.

Open your project ‘lums’ file from the Lumira Documents location with a compressed extraction tool like WinZip or 7zip and extract the contents into the folder.

Clear the odds out

Navigate to the extracted folder. You will see set of files. Lumira stores its configuration in its XML files. We will see about Lumira internals in an altogether separate series. Locate the file named “data_stream_0” which holds the data for the saved visualization.

Delete this file from the folder. This will remove the data from the Visualization. Now the next step is to pack the file back so that Lumira can read it.

Put the cat back in the bag

Select all the files inside the extracted directory (be sure not to select the directory itself) and use the compression tool to create a zip file.

You would get the zip file with the same name as your extracted folder. Now rename the file extension from “.zip” to “.lums”. Replace this file in the original destination.

Tip: If you are not able to see the extension, be sure to check your Folder options to uncheck Hide extension for known file type.

When you open SAP Lumira, you can see it does not show the data but the dimensions and measures you had used remains so that User has to just refresh the data to fetch it.


Publishing it in BI Platform

You can publish this to the BI platform and grant the Report user or the group only view rights to the Storyboard so that he can just view the data every time by refreshing and does not save the report back with the data.

When the user opens the Story board he does not see with any data in it.

I hope this Geek tweaks helps. Keep analyzing with SAP Lumira and look out for more Geek tweaks J

To report this post you need to login first.

2 Comments

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

  1. Tito Santos Silva

    Hi,

    just implemented this and works fine.

    Just one note that I must point out:

    – after you “purge” data this way, some data will still remain within your xml files. Just take a look to those files, and you will find (for example in document.xml) all possible values for the input controls, which are considered as metadata instead of regular data. These input controls may themselves contain sensible data.

    (0) 
    1. Shankar Narayanan SGS Post author

      Yes Tito,

      You are correct, Those XML files the dimensions and measures used along with the filter. The reason why i did not mention about it is because removing those would not keep the storyboard intact as the user has to drag and drop the dimension and measure everytime.

      I think its good to leave it there and use this to just refresh the data. Glad it could help you 🙂

      (0) 

Leave a Reply