> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/graphs-and-indicators/pareto/pareto-footer.md). # Pareto footer **Category:** Control **Version:** 1.0 **Last Updated:** May 21, 2026 **Author:** Any2Info *** ### Description The Pareto footer is a specialized mini designer available within dashboarding. It is used to create and manage Pareto definitions for Pareto controls. A Pareto definition determines how hierarchical Pareto data is generated and visualized. The configuration consists of: * A dataclip used as the datasource * A descriptive text for the topmost level * A calculation type * An action header on which the calculation is performed * A hierarchical layer structure based on dataclip headers The footer allows users to visually define drilldown layers by arranging headers from the selected dataclip into a tree structure. *** ### Configuration Options | Setting | Required | Description | | ---------------- | -------- | --------------------------------------------------------------------------------- | | Dataclip | Yes | The datasource used for the Pareto definition. | | Description | Yes | The descriptive label used for the topmost Pareto layer. | | Calculation Type | Yes | Determines how values are calculated within each layer. | | Action Header | Yes | The header on which the selected calculation type is applied. | | Layer Tree | Yes | Hierarchical structure of drilldown levels created by arranging dataclip headers. | *** ### Calculation Types #### Count The **Count** calculation determines layer values based on the occurrence count of values within a specific header. Each drilldown layer groups data by the selected header and counts the number of occurrences. Typical use cases include: * Counting orders per customer * Counting tickets per category * Counting records per status #### Sum The **Sum** calculation determines layer values based on the sum of the selected action header's values. Data is grouped by the current layer header and aggregated using the selected action header. Typical use cases include: * Revenue per customer * Quantity per product group * Total hours per department *** ### Layer Structure The Pareto footer allows the creation of hierarchical drilldown structures. Users can: * Select headers from the chosen dataclip * Drag and arrange headers into a tree structure * Define parent-child relationships between layers Each layer represents a drilldown level within the Pareto control. Example structure: ``` Country └── Customer └── Product ``` This structure allows users to drill down from Country → Customer → Product within the Pareto visualization. *** ### Usage Use the Pareto footer when creating dashboard visualizations that require: * Hierarchical data analysis * Drilldown exploration * Pareto-style aggregations * Grouped count or sum calculations Typical use cases include: * Sales analysis * Production analysis * Error distribution analysis * Customer segmentation * Revenue contribution analysis *** ### Tips & Best Practices * Use clear hierarchical structures to improve drilldown readability. * Avoid creating excessively deep layer trees to maintain dashboard performance and usability. * Ensure the selected action header contains compatible data for the chosen calculation type. * Use **Count** for categorical analysis and **Sum** for numerical aggregation scenarios. *** ### Limitations * The Pareto footer is only available within dashboarding. * It is only applicable to Pareto controls. * Sum calculations require numeric values in the selected action header. * The available headers depend entirely on the selected dataclip. *** ### Errors & Troubleshooting | Issue | Cause | Solution | | ---------------------------- | ------------------------------------------ | ----------------------------------------------- | | No headers available | No dataclip selected | Select a valid dataclip first | | Incorrect aggregation values | Non-numeric values used in Sum calculation | Ensure the action header contains numeric data | | Empty Pareto visualization | Invalid or incomplete layer configuration | Verify datasource, headers, and hierarchy setup | | Missing drilldown levels | Layers not correctly arranged in the tree | Reconfigure the layer hierarchy | *** ### Changelog | Version | Date | Change | | ------- | ------------ | ----------------------------------- | | 1.0 | May 21, 2026 | Initial documentation version added | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/graphs-and-indicators/pareto/pareto-footer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.