How to enable non-language options for PDF exports?
Analytics Plus unfortunately does not support Georgian. So if the data you have inside Analytics Plus is in Georgian then the exported PDF will contain blank values due to lack of font support. Here's how you can avoid this.
NOTE: This method is not version-specific so it can be applied to any version of analytics. Text instructions
1. Download this zip file from this
link.
2. Extract the zip. Inside you will find two files.
NOTE: Before you replace, make sure to take a backup of "pdffont.properties" which is already present under conf.
georgian=C\:\\<AnalyticsPlus_home>\\webapps\\ROOT\\themes\\common\\fonts\\micross.ttf Replace "<AnalyticsPlus_home>" with the actual analytics installed directory. Refer to the "After" screenshot.
Before:
After:
5. Copy the "micross.ttf" from the zip and place it under ManageEngine\AnalyticsPlus\webapps\ROOT\themes\common\fonts
6. Restart the Analytics Plus services.
7. Now you will find "Georgian" under Language in Export as PDF: Settings.
New to ADSelfService Plus?
Related Articles
Unable to export or email a view as PDF, Image, HTML - Linux Platform
Issue: Unexpected error when trying to export/email a view as PDF, Image, HTML Error trace: Caused by: javax.servlet.ServletException: com.phantomjs.export.server.ServerNeedKillingException: ServerNeedKillingException: Exception in phantom export :: ...
Steps to enable Google Analytics Connector
1. Stop the Analytics Plus services. 2. Modify the entry under <Analytics Plus home>/reports/conf/app.properties show.create.google.analytics.view=true Note: If the above property is missing, add them. By default the value will be set to 'false' 3. ...
Sync issue between SDP MSP and Aplus
Issue: Sync fails between ServiceDesk Plus MSP and AnalyticsPlus, after upgrading the SDP to 14730. Cause: An example of a case mismatch issue is when Analytics Plus seeks column alias names such as BillID, but MSP returns BILLID instead. This is a ...
Unable to start or access the application after upgrading to 4600 or 4610
Issues: Unable to start or access the application after upgrading to 4600 or 4610 version. Case 1: The application fails to start. Case 2: The application is started successfully but couldn't access the UI. Root cause: A few files were missing in the ...
Failed to upgrade to build 5300/5301
Issue: Upgrade fails while attempting to upgrade to the build 5300/5301. Cause: Upgrade fails due to a necessary system property required for logging slow queries is missing. This issue will arise while attempting to upgrade to the ...