← Back to ERP system builders
See how it helps
Chart tables and exports
Makes visualized numbers inspectable and exportable without losing filters, permissions or spreadsheet safety.
data-export-tabular-alternatives
Team members using this skill
When is it useful?
Use when users need the data behind a chart or a trustworthy download.
What does it help you do?
- Provides a tabular companion matching chart aggregation and filters.
- Labels whether an export contains raw, summarized, filtered or complete data.
- Enforces server permissions and handles encoding and spreadsheet-formula risks.
Try asking this
Add an export matching the filtered revenue chart, with readable dates and unauthorized fields excluded. Export a filtered quarter containing accented customer names and a formula-like value. Totals must match the chart and spreadsheet opening must not execute that value.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Data Export & Tabular Alternatives
Use this skill when building companion data tables, drill-through record views, or CSV/JSON/Excel data exports for charts and dashboards.
Verifiable Tabular Companion Views
- Every Chart Must Be Verifiable Against Underlying Numbers:
- Pair visual charts with an accessible, sortable tabular view (inline, tabbed toggle, or expandable drawer) showing the exact series, timestamps/categories, numerators, denominators, and formatted values plotted in the chart.
- Ensure totals/subtotals in the table footer follow the exact same weighted aggregation logic as the KPI header and chart summary.
Transparent, Permission-Safe Data Exports
- Explicitly State Export Scope: Raw vs. Aggregated & Filtered vs. Full:
- Label export actions unambiguously (
Export aggregated chart data (CSV)vs.Export filtered underlying records (CSV)). - Include or document export metadata: metric definitions, units/currency, reporting timezone, applied filter criteria, time window, and generation timestamp.
- Label export actions unambiguously (
- Enforce Server-Side Authorization & Tenant Boundaries on Exports:
- Never export data from unverified client caches or bypass field/row-level permissions.
- An export must respect the exact same workspace isolation, role permissions, and field-level redaction rules as the API and UI.
- Format & Spreadsheet Safety:
- Preserve exact numeric values (unrounded or minor-unit accurate numbers in numeric columns rather than pre-abbreviated
"$1.2M"strings that break spreadsheet sums), ISO-8601 dates, UTF-8 BOM when needed for Excel compatibility, and neutralize CSV formula injection prefixes (=,+,-,@).
- Preserve exact numeric values (unrounded or minor-unit accurate numbers in numeric columns rather than pre-abbreviated
Checklist
- Can users inspect the exact plotted values in a synchronized, accessible HTML data table?
- Does the export clearly distinguish between aggregated chart series and raw underlying records, and between filtered vs. unfiltered scope?
- Are workspace isolation and row/field-level permissions strictly enforced on every export endpoint?
- Are exported numbers exact (summable in spreadsheets) and protected against CSV formula injection?
Included files 1
SKILL.md
