cancel
Showing results for 
Search instead for 
Did you mean: 

Issue when displaying Category Titles and Y-Axis values in AnalyticCard Control.

FranciscoSAP
Advisor
Advisor
0 Kudos

Greetings experts:

I was recently handed the task of creating a Home page that displays several different Analytic Cards and KPI controls to provide our users with valuable information related to their pending work. I started with the simplest one in which I have to read my offline database and build a chart that displays how many different types of notifications the user has assigned to them, and how many Notification objects belonging to each one of those types.

Since I need these charts to be dynamic, I created rules to fetch the corresponding categories and amount of notifications belonging to those categories and assigned those rules to the "CategoryTitles" and "Data" properties of the Analytic Card control. (You can check the full metadata of my page here: https://www.codepile.net/pile/nVnBLDV2).

My rules are populating the "CategoryTitles" and "Data" properties with these values respectively:

As you can see, my chart categories are being populated with a simple array with 4 different items. And, for testing purposes, I hardcoded a deep array in the format that these controls expect to receive for the 'Data' property.

My end result is looking like this (I included a second chart with the default hardcoded values provided by MDK for comparison purposes):

As you can see in the above image I am currently facing 2 different issues:

  1. The values in my Y-Axis aren't being displayed, based on the height of each column it seems like the control is calculating the length of the axis accurately and is coherent to the data I provided to it, but the numbers 0 to 4 should be visible in it (as seen in the default example with the values 0 to 700,000).
  2. Only the titles for the first and last categories are being displayed, but this issue occurs in the default chart as well. According to the ChartCard Documentation, this is the expected behavior in iOS devices but I am currently testing this feature in Android devices exclusively by using my own mobile phone and Android Studio's device simulator.

Any ideas on how to approach these issues?

Accepted Solutions (0)

Answers (0)