nextgenSOFTWARE
SOFTWARE NEXT GENERATION

Nextgen Reports documentation

Nextgen Reports documentation — exampleExplore this topic with included sample inputs and engine-generated results
Open example ↗

All guides and demo UI are in English. Examples use fictional data. Programming is optional for report authors; application developers can start with runnable code.

Choose your starting point

Task Guide
Use the desktop application Desktop Studio on Linux
Run Studio Installation
Call the engine from application code Developer guide and complete examples
Integrate a .NET/Blazor app .NET client and Blazor viewer
Integrate Flutter/Dart Flutter SDK and Web demo
Create or edit a report Report authoring manual
Build forms and step-by-step dialogs Dialog Toolbox
Add validation, calculations and dependent choices TypeScript and events
Author template JSON or automate generation Template format, API/CLI authoring
Connect PostgreSQL, MSSQL, MySQL, MariaDB, SQLite, JSON or objects Data sources
Refresh HTTP data or transform snapshots HTTP sources, data preparation
Import data CSV/TSV, Excel XLSX
Export reports Office, HTML, page images
Add interactive report details Drill-down
Store versions and run scheduled jobs Library, server operations
Check scope and verification Roadmap, verification log

Learn by doing

  1. Open a sample project, change a parameter and generate Preview/PDF.
  2. Follow Build your first report in the authoring manual. Create a three-row table, heading and page numbers; save and reopen the project.
  3. Add a company parameter and test Cancel/Generate in the parameter form.
  4. Build two dialog pages with Next/Back and test required fields and sequential steps.
  5. Read the event guide and try samples/inventory.nrtemplate for validation and filtering.
  6. Run examples/EngineQuickStart to generate PDF/HTML/Excel/Word from C# and JSON.
  7. Open the Blazor or Flutter demo, change data and inspect the corresponding code guide.

Read in the browser

Studio Manual ↗ or Code → Manual opens the local English authoring guide. Its Developer guide & code examples link opens readable code, with links to local .NET, Flutter and data-source guides. The desktop launcher's documentation action opens the developer guide directly. No GitHub connection is needed. The developer hub uses three numbered cards to explain the learning path; code blocks have language labels, syntax colors and Copy code. A successful copy shows Copied. On restricted browser contexts, select and copy the text manually. Narrow screens stack the cards; long code lines scroll inside their code block.

Developer pages are generated from their Markdown sources by python3 scripts/build-docs.py; run it after editing those sources. The English browser manual is the source for the repository authoring manual; the same command synchronizes that copy. This prevents the two user manuals drifting into different languages. The verification log is supporting evidence, not a replacement for guides.