What's new ⬇ Download Reportworq
⬇ Guide PDF

Key concepts and the mental model#

Most Reportworq concepts fall into place once one idea clicks. That idea is the single most important thing a new user has to get.

Three things you build#

You create everything from the New menu on the Workspace, and three of its items are the building blocks of the product:

The distinction that matters most is between the job and the reports inside it. A report is content: the workbook, web report, or deck you add on the job's Reports step. The job is what refreshes that content and sends it out. What a run of the job delivers, the PDF, the workbook, the email, is its output.

Limits of a web report#

A web report has three limits, and none of them cuts your data without telling you. The numbers are the first version and will be raised as testing improves.

Limit The number What happens at it
Rows read from the source 1,000,000 rows per list or crosstab, and no more than 2,000,000 cells per report (an administrator can raise that to 5,000,000; in the Excel analyst pane on Mac and the web, all the reports in one workbook together may also hold at most 5,000,000 cells) A plain list with no limit of its own shows its first 10,000 rows (or the rows that fit on its sheet, if fewer) and says there are more; Load all rows reads up to the limit. A list that sorts, filters or ranks, and every crosstab on a data model, needs every row to be right, so above the limit it is not shown, and it tells you why. To read fewer rows, use a data model variable or a filter on the view in the data model (a filter you add to the report itself applies after the rows are read, so it does not help), or ask the report's author to set Rows read from the source to 1,000,000 or fewer, which makes the report work from only those rows and say so. In a distribution job, the report's live report file fails its run, with the reason in the step log. Cube crosstabs are not limited this way in this version.
Rows on the sheet 1,000 rows, columns A to AZ, in the web report studio and viewer A list taller than the sheet shows the rows that fit, keeps its Total under them, and says so ("shows 993 of the first 1,000 rows of its source, and its source has more rows"; its Total covers only the rows shown). The viewer and the downloaded file say it. A distribution job writes to Excel's whole sheet instead: every row goes out with its Total, and a report that would pass Excel's last row fails its sheet ("Nothing was distributed") rather than being cut.
Size of a saved report 25 MB (as stored, 1 MB = 1,000,000 bytes) Save refuses, and tells you the report's size and the limit. Nothing is saved and, for a report you are editing, your changes stay on screen: take a sheet, a picture or a large list out of the report, then save again.

A distribution job is a template that makes outputs#

Do not think of a distribution job as a file. Think of it as a template that creates outputs.

A finished PDF or a sent email is a result. In Reportworq, the distribution job is the thing that produces those results, over and over. It is a reusable asset with levers built in: parameters, variables, queries, formatting, messaging, and distribution rules. Pull those levers, and one job can generate hundreds or thousands of personalized outputs.

Different parts of the same source workbook do different work. Some parts exist to build the output file. Some exist only to build a rich email message. Others make distribution decisions, and others exist to collect data back into the planning system. Together with the job's settings, the workbook becomes a specification for how information should flow through the organization.

This is where new users most often get stuck: they keep thinking of a report as a document to send rather than part of a reusable system. Once you build one solid master workbook that a job can slice, personalize, and repeat, you stop maintaining a separate file per audience, and that is the moment the product pays off.

The terms that follow#

Everything else is a name for one of the levers on that template.

The value loop#

These pieces serve one repeating cycle: an author defines a distribution job once, Reportworq runs it (on demand or on a schedule) by refreshing the data and rendering each output, and then distributes the results to where people work. Because the job is defined once and reused, the authoring effort carries over to every future run. The full arc, from authoring through monitoring, is walked through in The distribution job lifecycle.

Where to go next#

Feedback on this page

Comments, questions, requests, or something missing or unclear? Email us - the page you are on is filled in for you.

Email feedback on this page

Or write to support@reportworq.com directly.