PlgReportStudio Plugin (Custom)

Open the practical lesson →

Current workflow

• Configure a business database at /dynamic-data/datasource, create a SQL dataset at /dynamic-data/dataset, then bind/design a Query report at /report/list.
• Fields come from SQL results, not direct SCADA channel/history APIs. Expose required history in a business table or view first.

Design, run, and save

• Insert current dataset fields with the designer panel, validate, preview, save, and reopen.
• FortuneSheet JSON is the template source. Current exports include HTML, PDF, and packages; inspect pagination, totals, and truncation warnings.
• Saves require the current template version. Reload and merge after a conflict rather than bypassing concurrency checks.

Storage and handover

• Report templates and metadata are in ReportStudio/ReportStudio.db; sources and datasets are in PlgDynamicData/PlgDynamicData.db under the runtime site.
• Back up both consistently. The current workflow does not depend on the old Admin MySQL database or MCP settings.