Episode 10: Building a Job - Sources
Quote from Karen Hewitt on October 16, 2026, 2:07 pmEpisode 10 kicks off a new stretch of the series. We wrapped up Output Options last time, and now we're stepping back to where every job begins: the source. This episode covers where your source reports can live, using PDF, Word and PowerPoint files as sources, making a source dynamic, and getting your brand fonts into the output. This video is slightly longer than previous but still under 10 mins.
Where your reports live: Reportworq only reads source reports from trusted locations called report providers. You set them up under Settings > Integrations > Report providers. The options are a network share, SharePoint, OneDrive, Google Drive, Box, Vena Reports, and IBM Planning Analytics application folders. In Reportworq 6 you can even store files in the Workspace directly and use those files as a report source.
PDF, Word and PowerPoint sources: Excel is still the report, but you can add a .pdf, .docx or .pptx on the Reports step and it gets merged into the job's PDF output. Its position in the Reports list is its position in the PDF, so a cover page goes first and T&Cs go last. These files are used as-is and only appear in PDF output, which makes them perfect for cover pages, disclaimers and appendices.
Dynamic sources: a source doesn't have to be the same file every run. Open the source's Properties and use Dynamic Path to build its location from a parameter, for example Cover Page - %param:Market%.docx. Each market's report then picks up its own cover page automatically. Two rules: the file names must match the parameter's display values exactly, and every value needs a matching file or the job will fail.
Custom fonts: if your template uses a brand font that isn't installed where Reportworq renders, the output falls back to a default font. Upload your .ttf, .otf or .ttc files to a workspace folder, then go to Settings > Configuration > Performance > Custom Fonts, check "Use custom fonts from a provider folder" and choose that folder under Fonts Source. The fonts reach every runner, including scheduled jobs, with no restart needed.
On Reportworq 5? Dynamic Path works the same way, from the source's Properties. Custom fonts work too, but the files live on the server: copy them directly into a folder the Reportworq service account can read, then enter that path under Administration > Configuration > Execution > Custom Fonts Folder and save.
Let us know if you have any questions!
Thanks!
Reportworq team
Episode 10 kicks off a new stretch of the series. We wrapped up Output Options last time, and now we're stepping back to where every job begins: the source. This episode covers where your source reports can live, using PDF, Word and PowerPoint files as sources, making a source dynamic, and getting your brand fonts into the output. This video is slightly longer than previous but still under 10 mins.
Where your reports live: Reportworq only reads source reports from trusted locations called report providers. You set them up under Settings > Integrations > Report providers. The options are a network share, SharePoint, OneDrive, Google Drive, Box, Vena Reports, and IBM Planning Analytics application folders. In Reportworq 6 you can even store files in the Workspace directly and use those files as a report source.
PDF, Word and PowerPoint sources: Excel is still the report, but you can add a .pdf, .docx or .pptx on the Reports step and it gets merged into the job's PDF output. Its position in the Reports list is its position in the PDF, so a cover page goes first and T&Cs go last. These files are used as-is and only appear in PDF output, which makes them perfect for cover pages, disclaimers and appendices.
Dynamic sources: a source doesn't have to be the same file every run. Open the source's Properties and use Dynamic Path to build its location from a parameter, for example Cover Page - %param:Market%.docx. Each market's report then picks up its own cover page automatically. Two rules: the file names must match the parameter's display values exactly, and every value needs a matching file or the job will fail.
Custom fonts: if your template uses a brand font that isn't installed where Reportworq renders, the output falls back to a default font. Upload your .ttf, .otf or .ttc files to a workspace folder, then go to Settings > Configuration > Performance > Custom Fonts, check "Use custom fonts from a provider folder" and choose that folder under Fonts Source. The fonts reach every runner, including scheduled jobs, with no restart needed.
On Reportworq 5? Dynamic Path works the same way, from the source's Properties. Custom fonts work too, but the files live on the server: copy them directly into a folder the Reportworq service account can read, then enter that path under Administration > Configuration > Execution > Custom Fonts Folder and save.
Let us know if you have any questions!
Thanks!
Reportworq team