Bundle Information
| Base | Advanced | Premier | |
| Library/Standard Template Dashboards | 3 | 4 | All Available |
| Custom Dashboards Per Year | 2 | 5 |
The following modifications are allowed for library/template dashboards: Cosmetic updates to colors, re-ordering existing widgets within the same dashboard, removing widgets from a dashboard, and updates to datasets (i.e., updating from Budget to Last Year or Forecast)
Getting to Know ProfitAbility
- ProfitAbility (PA) is Actabl's data visualization platform built on a popular 3rd party BI program. Currently, it only connects to ProfitSword's (PS) data. Data must first exist in ProfitSword to be pulled into ProfitAbility, and it must have a tag or GL account to be abstracted.
- There is an ongoing effort to integrate data from sister companies into Actabl's data warehouse. Once this development is complete, we will work to pull this data into PA for analytic purposes.
- PS is not a custom reporting tool or report writer. For custom reporting, we have other applications, such as API calls (based on bundle).
The goal of ProfitAbility is to visualize your data in a way that is going to make analysis and decision-making easier. Reports within PS provide raw data, whereas visualizations in PA transform that data into insightful representations.
- PA is not a live system, meaning data available in the PS database will not be readily available until the next cube spin.
ProfitAbility Expectations
- PA is not designed to replicate complex spreadsheets such as multi-tab Excel pivot table reports. Requests for complex dashboards, like those requiring weighted average calculations, will need to be reviewed for scope and discussed as they arise.
- Since PA is built on a 3rd party application, it does not automatically align with all out-of-the-box features. Additional setup will be required to extract certain information from PS and configure it for use in PA.
- By default, not all data from PS is available in PA; data must be selectively imported. Primarily, transactional and associated data are pulled in. For example, Vendor, Cashier information, and Variance Commentaries are not available in PA. However, reporting data for all sites and items, such as Balances, Quantities, Amounts, and Pace, is available.
- Use of API for certain custom/ad-hoc reporting is available based on your bundle. For example, this would allow report writing such as creating a balance sheet reconciliation report or side-by-side P&Ls. For assistance with setting up the API and executing these types of reports, please open a ProfitSword support ticket.
What is Good Dashboard Performance?
Dashboard performance refers to the time it takes for a dashboard to load. We aim to ensure our users have a positive experience when working with our data. Please note that the amount of information being loaded into the dashboard can impact load times.
Each widget in a dashboard represents a separate query. The dashboard sends these queries through the Microsoft 11S web server to the ElastiCube, retrieves the results, and then populates the data visualizations.
Custom Calculations in the Dashboard
Custom calculations are often useful when manipulating data to answer business questions. They allow users to aggregate data in various ways to present visually. However, they do not take time to process. Each custom calculation is a separate query that is processed within ProfitAbility.
Presenting Too Much Data
Presenting large amounts of data can significantly impact dashboard load times,. This is especially true when using pivot or table widgets with many rows. The web server must process and store the large data sets to display them visually. To improve performance, limit the number of dimensions that break the data into very granular forms.
We generally recommend using 6-8 widgets per dashboard for optimal performance. Each widget adds incremental query and rendering time. When a user loads the first dashboard in a session, performance will be slower compared to subsequent dashboard loads, as common web application elements like logos, toolbars, and code templates are loaded for the first time. Navigation between dashboards will be faster once these resources are cached.
Many to Many
A many-to-many (M2M) relationship can significantly slow down dashboard load times. In ProfitSage, there is a built-in, required M2M relationship between sites and site lists. Consequently, any dashboard that includes site lists will experience a noticeable performance decrease compared to a dashboard without site lists. This is because a site report is generated in the background for every site list available within the dashboard.
Accessibility/Data Security
An enrolled user can only filter and view sites/properties that they have been assigned to in ProfitSword, based on their associated email address.
Comments
0 comments
Article is closed for comments.