91.1 Best Practices¶
Recommendations collected from across this help, for designers, data modellers and administrators.
Workbooks¶
- One question per sheet. A sheet that answers one question – How are sales developing this year? – is easier to read than one with everything.
- Filters in the Filter Panel, so they apply to the whole workbook and travel with action links – see 7.7.
- Dynamic dates instead of fixed dates, so workbooks stay current – see 9.3.
- Table styles and themes for a consistent look; corporate colors for on-brand charts – see 11.4.
- Quick transformations for comparisons with last year and shares of total, rather than new metrics – see 10.4.
- Descriptions on workbooks and metrics – users and nikolAI find and understand them better.
Metrics¶
- Define common figures – turnover, margin, quantity – once as shared metrics with clear titles and descriptions – see 10.3.
- Set the number format on the metric, so it's the same everywhere.
- Build complex metrics from simpler ones.
Data Model¶
- Keep data that is analyzed together in one data warehouse; avoid combining data sources in queries.
- Map key fields to units consistently, so facts share dimensions – see 23.2.
- Give units clear titles and descriptions, and translate them for multi-language projects.
- Validate before every save that goes to users – see 26.1.
- Back up before big changes – see 26.4.
Performance¶
- Index the columns used for joins and filters – see 27.1.
- Use summary tables for large fact tables, and Collect statistics after big loads.
- Materialize slow, frequently used dynamic views – see 27.2.
- Keep tables in workbooks focused – thousands of rows are slow to show and hard to read.
Security¶
- Change the Administrator password, and give every user a strong password – see 32.2.
- Use user filters for row-level security, not folders.
- Install Modeller and Enterprise Manager only for administrators.
- Add SQL, script and program actions only when needed – they run without asking – see 13.4.
- Secure Datashop Web with HTTPS and remove its test pages – see 36.1.
- Use read-only database accounts for data sources.
Distributions¶
- Test with Test... before activating, and check the first status reports – see 18.9.
- Keep attachments small, and collate e-mails for recipients with many reports.
- Restart Acinta Server after changes.