We've been informed that there is currently a limit to only view 5,000 rows of data at a time in a cube, and only export 170,000 rows from a drillthrough in an Excel File.

Can these limits be increased so that we can see/export more rows?

It would be great to have the functionality to select more than one X-Axis at a time when creating a cube report, so that we get similar functionality to a Matrix (like in Microsoft SSRS) or an expanded Pivot Table (like in Microsoft Excel). This would allow for more detailed and spliced views and provide increased analytical value.

Add functionality for users to be able to reorder pages and page groups that have been Broadcasted

We would like the ability to alphabetically sort Member Group Labels that are created in KPI Admin --> Member Groups.

We would like the front-end script of cube reports in table view to be upgraded so that field sizing and arrangements will be saved even with large datasets. Currently we can only retain our formatting with small datasets.

For any agent status data blocks based on Realtime Indexsearch Configuration, we would like to be able to see all agents immediately when the page is loaded, as opposed to now where agents will only appear when their State/Status updates.

We would like the ability to be able to see who has made updates to a KPI and what those updates were within the KPI Admin page.

The virtual index has a limitation of not allowing new index's to be added in future, meaning rework after developing the mapping and re-creating measures if you want to add a new index at a later date.

It would be better if we could add the index to an existing Virtual index. This would mean less rework and far better user experience. It will be common for new index's to become available after the initial VI was created.

With Virtual index's a common requirement is field mapping via Member groups to create common fields in order to report effectively across all combined data sets.

My Enhancement request is to include the ability in eMite to automatically suggest fields when you create the virtual index for mapping. For example, date fields, Fields which contain the same underlaying data even though the column names are different. This would reduce time and effort with a much better user experience.

Allowing simple calculations within the measures box, as per the attached image. Would be good to have addition, subtraction for a starter, so we avoid having to create too many steps in a kpi.

Suggestion from Craig of AFSA:
"Add a disclaimer to the settings screen that says it doesn’t include current daylight savings time, automatically calculate the daylight savings time, or add an option to include it or not."

As an eMite administrator, I would like to configure my instance to authenticate users via OKTA for SSO.

It would be cool if you could annotate events to certain dates so that explanations for data anomalies caused by say a fire drill in your building or a website outage are right there on the chart or graph so anybody viewing it knows what happened.

Requesting an enhancement to the current functionality that allows users to view which dashboards have been shared to other users accounts, it would be useful to also have an audit trail (including a timestamp) of when these dashboards were actually shared or unshared.

It would be very helpful to have a feature to change the table view from daily to weekly to monthly by a simple click, as opposed to now having three different tables, one for a daily view, one for weekly, and another for monthly. Probably on the the table header (along with format painter, header style, grid/chart etc)

Ability to make use of the provided APIs for Zendesk chat integration.

Null value colour option for heat maps, currently shows 0 calls as Red (or most negative on colour spectrum). Simple option to make Null value a definable colour separate to the scale.

Looking for an SQL Server solution that I can manipulate and massage data as we see fit with the intent to use Power BI to consume that data.

I want to be able to include a secondary dimension to a Grid report so that it is included as an additional column.

For example, Calls Answered (Measure) & Agent Group (secondary Dimension) by Agent Name (Primary Dimension).