Every ReportPackage must be associated with exactly one site via siteId. This link determines which wells, sampling events, and analytical results are available for inclusion in the report. When you open a ReportPackage, Piper uses siteId to pre-filter all monitoring data to just the relevant site, preventing cross-site data from appearing in your regulatory submittal. Selecting the wrong site at creation time would pull in the wrong data, so verify siteId before adding sections and figures.
Technical section
Data model, API, and internals — visible to developers.