You can find details on how to install for Web, Library and Mobile in the respective install guide
Please restart the web server after deployment of Vitara charts. Additionally browser caches need to be purged and a new session needs to be started. If issue persists, use the following link (after substituting your server and port numbers) to check if the license key was replaced correctly and compare it with the key provided to you.
If you notice any unrecognizable character in the beggining of the file (as displayed in the browser), you should make sure that character is removed. You can just copy the contents without the character and paste it back into your license file. Then retry loading the document/dashboard.
If the issue is still unresolved, please contact firstname.lastname@example.org with details of the version, web server, steps taken and license key used for our tech support team to troubleshoot.
Please refer to our customization guide
Please refer to our customization guide
See our Contact Us page for details
Below is the link to the document in which how to hide the edit button is explained in detail. Enable/disable edit button
Hover the cursor on any of the vitara chart to get ‘Edit’ button. When we click on ‘Edit’ button properties popup window will be displayed on the screen. Click on ‘About’ tab in the properties window. The “About” tab will display details like; name of the chart, vitara charts version number, OS details of the client machine, browser details and time stamp etc.
This issue is typically caused by wrong configuration/deployment of charts.
First, please check to make sure the proper VitaraCharts plugin is deployed; In the case of mobile, the plugin to download is called VitaraChartsMobile.zip
Follow all the installation steps listed in the install guide for mobile.
Note that after deploying, the plugins folder will have several Vitara related folders (one for each type of chart)
In case a cluster of mobile servers are being used, it is critical to ensure Vitaracharts is deployed to all nodes in the cluster.
Also please verify that the version of Charts deployed in Mobile and Web both are same.
If you are using VitaraCharts for Documents please make sure that Display widget option in (iPhone, iPad,Android..etc) is enabled for the widget. </br>
You deployed charts correctly and still you are seeing a blank screen on mobile/library application in IOS or android device, please delete the chache of the application and reload the dossier/document. Generally, you need to do this when you deploy new vitara build or after Setting web configuration url to library/mobile application’s Vitara Charts config file.
Please note MicroStrategy only supports export to PDF of custom visuals from dossiers. When you export report services documents to PDF, custom visuals will be shown as a grid.
Please note that starting with MicroStrategy version 2019 Update 2, MicroStrategy has made changes to how the pdf export works and how it should be set up for custom visuals. You need to set up the visualization files locally on the export server.
IMPORTANT : Please use the web version of the VitaraCharts to set up the local resource folder on the export server
There are further troubleshooting steps made available by MicroStrategy. You can find them here
With dossiers, you may also see error messages when the export happens. For instance, the message could be something like Failed to display visualization: HCStackedBarChart because failed to get pluginsVisList from Failed due to NetworkError: Failed to execute ‘send’ on ‘XMLHttpRequest’: Failed to load
This is typically because of network configuration/permissions. You can also confirm this by trying to export a dossier with some other custom visual (like the D3WordCloud provided by MicroStrategy in the first row of the custom visuals). You will see the export fail with the same reason.
The access issues may arise from the type of user and authentication used on both machines. Here are couple of relevant links from MicroStrategy that describe this problem and also suggest some workarounds.
Please review and let us know if these apply to your case. In this scenario it is best to contact MicroStrategy to make sure best practices are being followed for setting up the network for export.
If the export is failing because of a different symptom then please contact Vitara support.
Prior to 4.2 font sizing was a little inconsistent and too small to be readable in most circumstances. In the 4.2 release version the styling in vitara charts is modified. Due to this the charts created 4.1 or prior version does not look the same when we open in 4.2 or above versions.
However, there is an easy way to revert to the old defaults.
Open customStyles.css located in VitaraCharts/custom folder. As shown below there is a section specifically available to revert to 4.1 styles.
You’ll have to just uncomment this section. For uncommenting, remove the leading /* mark and the last */ mark as shown below.
On the ‘About’ (as shown below) tab of the properties editor of the chart for which you want to find details, please click on the ‘Copy Chart Info For Support’ and paste into a text file and send it to the support team.
By default access to the vitara license from client browsers is left open using a URL of the format below.
However, access to the vitara license can be blocked by implementing the security constraints in the web.xml file.
The web.xml file will be available in the following directory.
Edit the web.xml file and copy and paste the below given security constraint just before the closing </web-app> tag.
<security-constraint> <display-name>Security constraint for Vitara license</display-name> <web-resource-collection> \** <web-resource-name>Protected Area</web-resource-name> \** <url-pattern>/plugins/VitaraCharts/license.txt</url-pattern> </web-resource-collection> <auth-constraint> <!--uncomment role-name to allow access for specific roles--> <!-- <role-name>admin</role-name> --> </auth-constraint> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </security-constraint>
At this point, the file is not accessible to any user. Now you need to make sure the right role still has access to this file
Save and close the web.xml file and restart the webserver.
For your reference, below is the screenshot of the web.xml file after adding the above security constraint code.
In order to make only a subset of the charts available to the users, one of the configuration (xml) files needs to be modified. Under the VitaraCharts folder (under MicroStrategy Web plugins folder), you will see the following set of folders and files. The specific file to be opened for editing is VitaraCharts/WEB-INF/config/visualization.xml
Please make a backup of this file before making any changes.
This file lists all the visuals that VitaraCharts includes. There are separate sections for each type of client (Web listed as ‘ajax’, ‘ipad’, ‘iphone’ etc) You can make changes under the ‘ajax’ visualization-list to restrict dossier authors from seeing all of the vitara plugins
Under this list, comment or remove specific visualizations that you don’t want to show your users. For instance, if you do not want to use the Vitara Bar chart, the highlighted section below should be commented or deleted.
You do not need to make changes in any of the other sections (like ipad, iphone etc) because once the chart is removed from the ‘ajax’ section, it is not available to dossier authors. The other sections are only used for rendering the authored dossiers.
Once all changes are made, save the file and restart the web server. Please read through the error logs and make sure MicroStrategy did not have any issues with loading the file (in case there was an error in editing the file and the format of the xml becomes invalid).
When it is time to upgrade to a newer version of VitaraCharts, you will need to make sure you make the same changes on the latest version of visualizations.xml
For reference the structure of the visualizations.xml file is documented here MicroStrategy Visualization xml spec
VitaraCharts does not use or have any dependency on log4j. So there is no change required with respect to the specific vulnerability for Vitara plugin.
The below article contains MicroStrategy recommended actions to help maintain the security posture of your MicroStrategy environment against log4j vulnerability.
MicroStrategy Response to CVE 2021