1 2 3 14 Previous Next

SAP BusinessObjects Dashboards

200 Posts

One of the common requirements we see for maps for SAP BusinessObjects is creating geographic choropleths / heat maps. In this scenario, you can view common administrative areas or custom territories (country, state, etc) with a single measure at a time. In this article, I wanted to share an approach that my team has been championing with customers over the last 6 months. The idea is to use SAP Dashboards as rapid designer for embedded analytics. Most important, we can use the HTML5 output, not just as Flash. With SAP tools themselves having limited integration, we wanted to figure out a good way to get as close to possible for "design once deploy everywhere" when it comes to maps.

Notice: The instructions in this tutorial rely on third party, certified integrations for SAP. If you are not interested in reviewing solution using third party tools, this may not be an article of interest.




Required SAP Software:
SAP Dashboards for BI4.1

SAP Design Studio

SAP BusinesObjects 4.1 SP03-SP04 preferred


Required Third Party Tools:

Dashboards: CMaps Plugin for mapping

Webi: CMaps Analytics Webi Extension (included with CMaps Plugin)

Design Studio: APOS Dashboard Migrator for Design Studio


The concept of a choropleth is simple! Use the values from a measure to drive color intensity from high to low in a geographic map. This kind of visualization is good for quickly identifying outliers (high and low). However, Choropleths when used against geographic boundaries can be deceptive for several reasons.. View Choropleths and Heatmaps Intro and Best Practices for more details.


Without going into click by click steps, I have highlighted the important steps to produce a US Choropleth across all of the major SAP tools. I provide the project source files below:


Create your Choropleth in SAP Dashboards

(download the complete dashboard template here)

  • Drag the CMaps Plugin map component onto your canvas and open the property sheet
  • Select "Shape Data" and then paste the URL to the World Shapefile. If you have another geography in mind you can our free Shapefile Explorer.
  • In this dashboard template, we have data for World Countries with a few measures (sales,expenses, etc). Additionally, we have a selector that allows you to choose between the two measures using dashboard column insertion.
  • From the selected measure, we calculate the min, max, and midpoint to give us our Choropleth levels. This technique grants you with complete control over the logic so you can potentially ignore outliers. You can also use this with out of the box maps that ship with SAP Dashboards.


  • I included some sample, colors in the spreadsheet, but if you want custom heatmap colors, you can use this free choropleth color generator
  • As the last step, we bind our colors to the Colors property and choropleth logic to the Limits property, on the CMaps Plugin alerts tab.



All of the above steps can be easily reversed engineered in this free template along with a copy of CMaps Plugin


Now we have our functional choropleth with hardcoded data that we can connect to a live query, or prepare it for use with Webi and Design Studio


Prepare for Webi and Design Studio:
For embedding SAP Dashboards in Webi or Design Sutido, you will need to create an external interface inside of SAP Dashboards using the Data Manager.


For Webi, create an external interface with the following properties:

Range Name: GetReportData

Range: Bind it to the data range containing the raw data for your map. This range will automatically be replaced by a Webi report part data.

Access: Read/Write


For Design Studio, create an external interface with the following properties:

Range Name: Range_0

Range: Bind it to the data range containing the raw data for your map. This range will automatically be replaced by a Webi report part data.

Access: Write


That's it! Your map is now ready for use with Webi and Design Studio.



Export your Geographic Analytic to the SAP BusinessObjects repository

  • Go to the repository, right click on the new dashboard object, select Properties and get the iDocID and the CUID.

You will need both of these values for Webi and Design Studio publishing. APOS Dashboard Migrator for Design Studio does have a feature to browse the repository and quickly get this information.



Embed and Capturewebi.JPGView your Geo Heatmap in Webi

This step requires installation of CMaps Analytics Webi Extension


  • Open the Webi Report containing your data
  • Go to Design mode in Webi where you can edit your report layout and objects
  • Select the Webi extension icon on the left icon pane.
  • Paste the Dashboard iDocID and press "Save". This will load your dashboard object
  • Click in the report to select the report part which you would like to load into your dashboard. The extension will automatically capture what report part you selected.
  • Instantly, only the countries in your report part will appear on the map along with shaded regions


View your Geo Heatmap in Design Studio

This step requires installation of APOS Dashboard Migrator for Design Studio


  • Open Design Studio
  • Add the APOS Dashboard Migrator Component
  • Fill in the connection details for APOS Dashboard Migrator (system name, BOE credentials, etc)
  • Select the CUID from the "Additional Properties" pane.


  • Select a Data Source which connects this component directly to a query. In our example, we created a Universe data connection with a Country and some measures:


  • Fill in the external interface definition which will load the contents of the query into the Range_0 external interface we created in our dashboard.

{"send":[{"range":"Range_0","dataDS":["Country Name","Population","Sales","Expenses"]}]


  • Select the dashboard type as Flash or Mobile (HTML5)- This is one of the great aspects of APOS Dashboard Migrator. You can absolutely use the HTML5 version of the dashboard object which does include CMaps Plugin (HTML5 Supported).


  • Preview your dashboard from Design Studio to view your data. Additionally, you can use interactivity, filtering, and even use the map to drive additional events just like any other component.



What's Next?

We are just scratching the surface for what is possible here, so I am excited to see how customers push us further to simplify and enhance these capabilities.

Hi Pals,

Best steps to develop dashboard


1)Understand the user requirement clearly(This most IMP step, If you go wrong here you may need to start from zero.)

2)Try to understand client business and try to give better model than client suggest.

3)Draw a prototype of Dashboard in white paper.

4)Analyse which features are possible in MOBILE/DESKTOP environment.

5)Make final dashboard prototype.

6)Based on above discussion decide which type of connection and source developer should use.(Out of12+ connection choose best which is suitable for your        scenario.)

7)Keenly understand pros and cons of your chosen connection, source.

8)Start developing Dashboard

9)Save dashboard as different versions(Save after every major changes you do in dashboard )

10)Based on type of connection used in dashboard, movement of dashboard from DEV>>>UAT>>PROD differs. Understand the strategy of movement.

11)Keep the client informed on the development front.

12)Final step move to production. GO LIVE.





     Publication is used to publish report like webi intelligence, desktop intelligence, crystal reports.The report or document is published/distributed to several users or groups. It is also helps personalize the data of report for the user before it is published. This would help user view only his/her data.
An instance of the report is generated for the users which can be sent to their inbox. Later the generated instance of the report can be used in dashboards.

     This blog would help publish the webi report to user’s inbox.  We will personalize the webi report i.e. we will restrict the data that should be visible to the users.

     For publication, we need to create profile for users mentioning what data should be visible for that particular user. Later we would be publishing the webi report and consuming it in Dashboard using BIWS.


A] Creating webi report


-->Create a webi report on efashion universe. Select State and Sales Revenue in result objects.






àSave document to enterprise in the desired folder.





B] Creating profile


àLogin to CMC. I assume that you have users created and they have the required rights to view the webi report. Here I have users A and B with view on demand rights.

àLet’s create profile for the users specifying the data that should be visible for them. In CMC, go to Profiles. Select new profile.





àGive a name to the profile. Select Ok.




àRight click on the profile. You will see Profile Targets and Profile Values. The targets are the objects which have to be restricted. Here it is state. Select the Profile Targets.




àClick Add.




àSelect the universe that was used to create the webi report. In this example we have used efashion under the webi universes.




àClick on Select object from the universe to select the object i.e. state and click ok.




àThe profile target set is state. Select the checkbox and click ok.




àGo to profile values and click on add.

Now select the first user. We could also choose group in case a group of users need to view the same data and the other group of users need to view the other data. I have selected user A.




àProvide value for the target i.e. state for this selected user.

We could provide the value manually or select filter expression. Select web intelligence formula expression. This opens the Formula editor. Click on the formula editor button and select the value. Click ok. Here I want the user A to see data only for California and Colorado.



àNow add the profile values for the other desired users in the similar manner. And check the selections as below:



C] Creating publication


Go to the folder where you want to create the publication and select New -> Publication




àProvide a name under general properties
Go to source document and click on "Add" to add the source document i.e. the report to be published.



àIn enterprise recipients we can select the users for whom we would be publishing the report. These are the users that are present in the BO enterprise.
The Dynamic recipient are the users who do not have account in BO Enterprise, their information is present in external data source such as database or AD directory.





àGo to Personalization. Here we would be selecting the profile. Under profile we have selected what data will be visible for a particular user when we publish the report.





àUnder Formats we can select in which format the report should be published. Here we would keep it as webi intelligence.




àUnder Destinations we would select the BI inbox as we would be using the latest user instance in dashboard. If we select Default enterprise location we would have to set GetFromLatestDocumentInstance to 1.





There are other additional options that you could explore.

Now save and close the publication.

àRight click on the publication and select Run now. We could also schedule the publication and run it as per our requirement.





àRight click on the publication and select History to check the status of the publication.




àLogin to launch pad as user A. Go to inbox. Open the instance generated.





We see that the user can see revenue only for the selected states.

Check for the result for other users as well.



D] Creating BIWS and consuming it in Dashboards


àNow create a web service on this webi report to consume it in dashboard.




àLaunch dashboard. Go to data manager and add QAAWS connection.

Paste the WSDL URL and click import. Select Get ReportBlock method.

Under the input values set getFromUserInstance to 1. Under the output values map the table cell and header cell. (Setting Refresh to 1 in input values is not necessary.)





àUnder usage tab set the refresh to "refresh before components are loaded" as we do not have any prompt value to specify.

àPull a spreadsheet component to canvas and map the display data to the excel range containg the data.





àPreview dashboard as administrator:




àNow preview it as a user (User A)




So using publication we could restrict the data that is to be displayed to the users.

Hi All,




This blog gives an overview and some design tips for designing Dashboards using the BEx query for Beginners.


As we all know that the today's requirement for using BEx in Dashboards is steeply increasing and also SAP have made better integration of BEx with Business Objects Dashboards.

It is suggested that we follow a Process in designing Dashboards which will give us the better control and also reduces the unnecessary rework.


  • First, getting the Proper Requirements from the Client/Customer  is very essential. If not, you will have to rework in design, logic and also creating unnecessary frustration.
  • Freezing the requirements  is the first step in the Process and  should be given the highest priority. So, it gives us proper direction to get ahead.

        But being a beginner, the probability of interacting with the Customer/Client is low.


First, we need to understand the Connection between Business Warehouse(BW) and Business Objects DashBoards.


BW - Business Warehouse

CMS - Central Management Server

DB - DashBoard

OLAP - Online Analytical Processing

U1,U2,U3,U4 - Users

RC - Relative Connection


CMS  is Central Management Server and  the heart of SAP Business Objects Enterprise System which includes User Authentication, CMS

Database, access rights etc.


We can create a dashboard in the local Workstation but if we want to publish it in the server then we need to have a user(Named or Concurrent) in the CMS .

A user is created in the CMS by the Administrator. Users are given different access levels. For Example, a beginner is given access to only few folders in the CMS  whereas Admin will have full access.


A Session will connect a User to the CMS server by just logging in using the credentials. We can create a Session in IDT( Information Design Tool) or UDT

(Universe Design Tool). Once the session is created and  opened, it will display all your Connections, Universes and files that are under your access levels in the IDT.


Now, we need to create a connection between BW server and CMS server to access the Query. So, we will create the connection in IDT as OLAP connection

through  BICS client. BICS interface is the only connectivity to SAP BW from SAP Business Objects.

To connect to other data sources, we shall use the Relational Connection.

Finally, Publish the connection in the Repository so that when you add the query in the DashBoard, you will see this connection and so you can use it.




Finally, User is created by the Admin and session is opened in the IDT. An OLAP connection is also established between BW server and CMS through BICS which will interact with the BEx query.



The below screen shot gives us the simple Process in designing the Dashboards. It starts with 'FREEZE THE DESIGN' . In future, the customer may come with some new requirements so cycle starts again.







Before we open the Dashboards in our Workstation, it is better that we start designing on  a sheet of paper. This makes us to analyze many parameters like

  • Placement of Components
  • Types of Charts
  • Layout Designing
  • Building the Logic for KPI's
  • Where to use Dynamic Visibility for displaying different KPI's
  • How to use less Mouse clicks/operations
  • Less Navigation, More Data Visibility   (etc..)


Once we have made  an analysis of the design, then we shall go ahead in designing on screen. Because, designing on a sheet of paper gives us clear idea of

everything we need on DashBoard. This method of Designing on sheet of paper  will make us confident because we are mentally prepared about the design.



Now, it's time to show our creativity on the screen.

User Experience is very Important in dashboards as the Customer expects a pleasant feeling in using it.

Everyone of us are creative and to make the end user addictive to our dashboard, then we shall understand some science behind the User Experience.


Check out the  below link  about the "Cognition & Intrinsic User Experience"




We know to add and edit  the query but understanding the importance of Filter option is essential.

  • Bex queries may have mandatory fields in the selection screen. So, it's a best practice to use filters to extract only the required data from BW  to dashboards which will significantly reduces the load and provides faster performance.
  • Preview the result and in the final screen try to uncheck "Refresh the query before components are loaded".
  • After you uncheck this option, it  will load all your components first and then refreshes the query so that the end user will not wait with the empty/white screen.  
  • Now carefully bind the data to the excel and take snapshot to check the incoming data.
  • Use different colors  in the Excel sheet to  indicate Incoming Data from Query, data mapped to some components etc... and at the same time use less colors to avoid complexity.
  • Give the description of each color in the excel Sheet so that the other user can understand your purpose.
  • Use description for individual/Group of cells which are used in the query so that any user can understand your excel sheet.
  • Don't perform complex calculations in the Excel sheet as it degrades the performance.



Most of the errors come from incorrect linking of  the components so I suggest you to remember the below three points.

Take a component and

  • Get clear with the Source and Destination of the Component. Map them. If the component has to be interactive, then do the required settings for it.
  • Identify the dependent components of it and do the settings as required.
  • Snapshot it and check the data.



After all the components are properly mapped, then preview the data.


You can select any of the two options depending upon your needs as it gives us perfect sizing and the perfect look on the screen.

  • View ----> Canvas Sizing ------> Fit canvas to components
  • View ----> Canvas Sizing ------> Fit canvas to window



The dashboard can be previewed in different formats.

  • Flash
  • Presentation
  • Word
  • PDF

Then save it to the Repository and also locally in the available formats.

  • SWF (Flash) file is very useful as you can view the dashboard on the fly in your Internet Browser  as you don't need the SAP Dashboards to be installed in your computer.
  • If you want your dashboard to be run only in the Desktop, then choose

          File ------> Save Platform as -------> Dashboard Object as desktop only

  • If you want your dashboard to be run both in the Desktop and mobile, then choose

          File ------> Save Platform as -------> Dashboard Object as desktop and Mobile

  • Check the mobile compatibility of the  components as few are not supported.


Finally, launch the 'Launch Pad' and view the Dashboard that you have created.


I felt sharing to all of you  which I learnt along the way and also believe  that  this blog gives you some overview/idea and tips about the Dashboard.


Thank you a lot  for reading this blog !!!!! 

I am pretty sure that most of us have encountered with the below problem while working with line charts/barcharts in   Dashboards ie, the y-value are repeating for the graph, or the value plotted is not correct.


Suppose the values to be plotted in the graph is as shown in below.


Excel values.JPG

The value plotted in graph will be as shown below


First image.JPG

ie, the value 2 is plotted  in between 2 and 3, instead of plotting at the line of 2 itself.

It is because the height of the graph is less. If we increase the height of the graph, the graph looks like as shown below.


Second image.JPG

Here the Y-axis values are repeating.

Giving decimal values to the scale will not solve the problem, and it is not acceptable at certain scenarios (Eg: plotting age, count etc..)

In order to avoid these problems, we have to customize the scale.

Below steps explains how we can customize the scale.


1.    Right click the line chart and go to the behavior tab.

       By default, ‘Auto(Y) axis’ is selected. We have to change it to ‘Manual(Y) Axis’ for customizing the scale

2.    ‘Size of Division’ and ‘Maximum Limit’ and ‘Minimum limit’ (If ‘_’ ve values needs to be plotted) are the parameters to be set.

       While selecting the ‘Size of division’ and ‘Maximum limit’ and ‘Minimum limit’ we should be careful.

3.    Below steps can be used to find the ‘Size of division’ and ‘Maximum limit’

       a)    Find the ‘Maximum’ and ‘Minimum ‘values of the numbers to be plotted in the graph.

              Let Maximum be ‘Max’ and Minimum be ‘Min’

       b)   If (Max<10 or ((Max-Min)/2)<10), then S=Max/2

              Else S= (Max-Min)/2,   Where S is ‘Size of Division’

              Round down the value to the nearest integer.

      c)    Find the remainder after the ‘Maximum’ value divided by ‘size of division’

             We can use the ‘mod’ function available in excel for this.

             Remainder (R )=mod('Max','S')

     d)    The Maximum Limit ‘MaxLim’ can be found by using the formula


     e)    If ‘-‘ve values needs to be plotted, we have to find the Minimum Limit value .(We can use the steps ‘c’ and ‘d’ with some changes to find the ‘Minimum limit’)

             If '-' ve value are not there, we can set the ‘Minimum Limit’ to 0.

4.    As the last step we have to map the ‘Maximum Limit ‘ to ‘MaxLim’ and ‘Size of Division ‘ to ‘S’


      Now the values in the graph are plotted correctly.By using the ‘Mouse –Over values’ property we can see the exact value of each point as shown below


     Mose over image.jpg

The above implementation worked fine, for all scenarios in our recent project.



Hope this will be useful...


     The Dashboards application crashes when we try to launch Dashboard Designer on a machine where secured web access or proxy settings are applied.




When the Dashboards application is launched, the startup page of the designer connects to the internet ( www.sap.com, www.businessobjects.com etc) . This causes Designer to crash when security for web access is applied or due to proxy settings.





     We can disable this security access manually.


     Following are the steps which restrict the designer to access the web.


  1. Go the following folder Dashboards Installation dir\Program files\SAP BusinessObjects\Xcelsius 4.0\assets\startPage\en\js
  2. Open the javascript file start_function.js
  3. Search for the function onInitialize()
  4. Comment line : InitializeResourcesTag()



   5. Save the file.

   6. Re-launch Dashboard designer.



Hello all


This post is useful for beginners. After inserting graph,Y axis values will change

depending on the input. Ex : 50000000,20000000,150000000. as shown in column

chart Fig (a). These kind of values reduces the size of the graph.

To solve this problem we have to select the Fixed label size check box in Behavior Tab.

Then values are changes as fallows 50000000=50M,20000000=20M etc.

it will work for both manual and auto value mode.

                                                    Fig (a)

select fixed label size check box as shown in image




Values will display as shown below.


In few cases we have to represent 10000 as10T, but by default dashboard will display

10000=10K. To change "K" to "T" we have to fallow the fallowing steps

click on the image as shown below



Below dialog box will appear


click on particular row where u want to change Display sign ,

assign sign depending on requirement Then click OK






I'm pretty sure that most of you dashboard developers must have encountered the "Request Processing Failed ( XLS 000009) null" error.


Request processing failed - NULL.png


Background information:


There were certain things that I found strange about this error:


a. Lack of proper error description, which made debugging difficult

b. Sporadic occurrence of the defect (say once a day or once in 3 days)


When you receive this error, you know for sure at least one of your queries was affected by this, as this affected query would not fetch any results. However the next time you receive this error, some other query must have stopped working. This was when we realized this error had nothing to do with the dashboards queries or dashboard design.


Root Cause:


After getting in touch with the SAP support team regarding this defect and after proving the necessary background details like the iPad error log, screenshots, product versions etc SAP concluded that this was not a dashboard design issue, rather a network congestion issue.



As mentioned earlier, this has nothing to do with the dashboard design. In many other posts, saw comments from other fellow members asking to restart services, create 64 bit DSN entry, update with latest patch etc, none of which worked for us.


As per SAP support, this error states congestion in the network. This could mean one of the 3 below:

a. existing servers and not able to bear the load/ requests

b. network issues between the geographical location when server is available and where the request is generated from (say your BO server is in USA and you are trying to run your dashboard from India)

c. network connection speeds across the client location and/ or developer location (office internet speed)


for points (b) and (c), there is nothing much that the SAP support/ BO admin can do.

However for the first point (a) SAP asked our BO admin person to add two more servers by cloning the existing DASHBOARD PROCESSING SERVER and DASHBOARD CACHE SERVER.


Believe it or not, this resolved the issue.


Since the day this resolution steps were implemented in our DEV and SIT environment, we haven't received this error even once. I hope this is a permanent solution that SAP provided. We are constantly monitoring the dashboards in both the environments.

URL Button is a standard component that can be used to fire up a webpage, openDoc URL, etc. This button is used extensively for allowing users to click and open reports and webpages. The same component can also be used to dynamically populate URLs according to the user selections and open them automatically on scorecard, table, list, etc. interactions (using a single URL button component). This reduces the excel logic and the component count in the dashboard. Also, using a single component reduces maintenance overhead.

Let us look at how to use this functionality.

1. Let us start with using a URL button and a scorecard component.

2. Select the scorecard component and bind it to the Display Data and Data Insertion. Set the appearance, general and behaviour properties as required.






3. Now, select the URL button component and map the URL to an excel cell.


4. This cell will be populated dynamically based on user selection from the scorecard.

5. Go to the Behaviour tab in the URL Button properties and select the Trigger Cell as the same cell in #4. Select “When value changes”.


6. Now, every time the user selects any of the rows in the scorecard, the respective link will be fed to the URL button and the same will be fired up automatically.

7. You may use the same logic to populate openDoc URL parameters. Eg : Insert plant from the scorecard and populate in the URL accordingly. http://....../&prompt1=Plant1 or http://...../&prompt1=Plant2 , etc.

8. You may use a pie chart, or a column chart or any other chart component (instead of the scorecard used in the example above) and achieve the same result. This method can be used for hyper-linking charts and other components which are dynamic in nature.

In one of the ongoing BO implementation projects, we had a peculiar requirement of allowing users to select multiple parameters. In our case, we had to select multiple planners and filter dashboard data accordingly.

Apart from the List Builder component, there is not much scope in the default Xcelsius components to satisfy this requirement. List Builder has its own pros and cons. The user is not very motivated to use List Builders because of the real estate it occupies and its design. 

We bundled some standard components and created a multi-select. It looks like this:


We have used a combination of multiple check boxes put inside a canvas. This canvas “drops-down” when the “Select Planner” button is clicked and “hides” when the cross button is clicked. We have driven the dynamic visibility of the canvas on the button interactions.

Individual checkboxes are capable of data insertion. These inserted values can be used to drive the excel logic further. An “ALL” checkbox is provided at the top of the stack that supersedes all the other selections.

Clients always have the requirements for tooltips on the dashboard. While charting components have the default tooltip available, it is yet not a default functionality for a lot of components like images, buttons, labels, etc.

One of the methods of achieving the tooltip is using a transparent URL button. URL buttons have tooltips. Although this is a long known method, it has a major con – the tooltip font cannot be controlled, it is too tiny to be readable.

Another interesting but tedious way is to use a transparent Toggle component and a label. Let’s look at this approach.

  1. Select a push button, a toggle button and a label.
  2.      1.png
  3. Align the push button and the toggle button completely and make them “same size”.
  4. The toggle button should be on top of the push button and should completely align with it. Off course, it should be transparent.
  5. Place the label according to you convenience and enter the tooltip text in it.
  6. Go to the properties for Toggle button and set the Data insertion values.
  7. 2.png
  8. This destination will be driving the dynamic visibility of the label.
  9. Go to the Behaviour tab of the toggle button properties and set the insertion on “mouse over”. Selected item should be “off”.
  10. 3.png
  11. Now, set the dynamic visibility of the label component to the same cell as the toggle button destination.

Whenever the user hovers the mouse into the push button the tooltip (label) becomes visible and it goes away when the user hovers out of the push button. The aesthetics of the tooltip(label) can be controlled through the label component properties.

We face real estate issue when we design the dashboards such as placing the scorecards, charts and try to squeeze in too many columns. We end up facing challenge like displaying values cut off, or enabling the scroll bar.


For scorecards, we need to enable the property "Rows are Selectable" from Behavior -> Common tab.

Scorecard - Selectable.png


Find below the example where values get cut off and unable to read the complete text. If required, user tap on the text for 2 seconds, text will be display the entire text as small pop-out.




When it comes to Line chart, when user have a long press on the chart brings up the legend value which is quite a nice feature.

Chart - Selection.png


Multi-selection is a widely required feature when it comes to dashboards. We have List Builder for Desktop version of dashboards. However, we dont have any choice for mobile dashboards. Here is the interesting work-around for the multi-select. The out of box property of Line chart helps here.


Instead of creating multiple combo-boxes & check-box to enable and disable the selection, the line chart comes handy.


Insert the Line Chart and Select the Appearance Tab.



Scroll down and check the Enable Legend property. Check Enable Hide/Show chart series at Run-Time -> "Mouse Click". This property is supported in Mobile.


Enable Legend.png


Preview the dashboard on iPad. Here you go...


Multiselect - 11.png


Tap on Market Share (Prior Period) and Quota, so that it will be disable for comparison.


Multiselect - 12.png


One another creative component. Which can be made easily, which looks classy and catchy.

It may be little longer than my other blog posts , but bear with me, because the result of this is worth the pain.


So this is how the Component look like.
















This one is for the reference. I2 and J2 cells are filled with the corresponding colour of G2 and H2 respectively

where in R is red, G is green and, Y is Yellow.


Thats how it is done. !




Thanks for Reading.


.xlf is enclosed for more clearer explanation. Change the extension to .xlf to use the same.




Sara G

Creativity With Pie Charts

Posted by Sara G Jun 26, 2014

Creativity in the Charts can make the component look different altogether. Here is one such example.

Follow the screen shots below to achieve the different views of a simple Pie chart.



Tube/Donut Chart


Wheel Chart




Concentric Pie Chart



Double Donut Chart



For the chart representation , suppose here the smaller one shows the Current Year and the Bigger one

shows the Previous year. The legends of this can be taken form the Character Map. The below screen shots

shows the further explanation to this, i.e. How it can be achieved.


With that said, the ellipse can be used to have a all selection as well. Just by placing a transparent push button.

Double Disk.PNG

Sample Visualizations :


Disk Chart.PNG


Double Disk_1.PNG



Thanks for Reading.

.xlf is enclosed for more clearer explanation. Change the extension to .xlf to use the same.





Filter Blog

By author:
By date:
By tag: