Reporting Operations
Part of Selecting BI and dashboard software
Checking export and embedding capabilities during a trial
Verify BI exports and embedded reports with the users, permissions, file contents and authentication your delivery route requires.
For a BI software trial, define the exact file or embedded view, its audience, the data it may expose and how users will authenticate. Check the output with the intended user's permissions. An administrator's menu option is not proof that the delivery route works for its recipients.
Define each output
A PDF for a monthly meeting, a spreadsheet of summarised figures, a row-level reconciliation file and an interactive report inside a customer application are different requirements. For each, record the audience, allowed fields, filters, update point and need for interaction.
Use a controlled dataset with a restricted field and a small, known set of rows. Prepare the expected result for users with different access. Inspect the file or embedded view itself, not a success message.
End-to-End Verification of BI Output Delivery
- Define output type and audiencee.g., PDF for monthly meeting, interactive report in customer app
- Prepare controlled dataset with restricted fieldsUse small, known set of rows for consistency
- Export as intended user and inspect fileCheck format, row count, columns, date format, summary vs detail
- Test embedding in target environmentVerify sign-in flow, access control, filter functionality
- Record pass conditions and limitationsInclude user role, licence type, settings, and unverified cases
Inspect the export
In the Power BI service, summarised and underlying-data exports are distinct options. Availability and contents depend on permissions, report and administrator settings, the visual and the format. Tableau Cloud offers formats such as image, data, crosstab and PDF, subject to content permissions and format-specific behaviour.
Looker downloads require download_with_limit or download_without_limit permission; options vary by content and format. None of these documented options guarantees that a particular user can obtain the file you need.
For each candidate, export as an ordinary intended user. Record the visual, filters, format, row count, columns, date representation and whether the file contains summary or detail. Compare it with the expected population.
Check a user who should be denied detail as well. If scheduled delivery or an API export is required, assess that route separately from manual download.
Export and Embedding Capabilities Across BI Tools
- Power BIExports: Summary & underlying data; controlled by permissions, visual, format, and admin settings. Embedding: Requires Pro or PPU licence unless on qualifying capacity.
- Tableau CloudExports: Image, data, crosstab, PDF; subject to content permissions and format-specific rules. Embedding: Uses connected-app authentication with domain allowlisting; separate site and app controls.
- LookerExports: Requires `download_with_limit` or `download_without_limit` permission; options vary by content and format. Embedding: Private (requires login) vs. signed (application-based).
Check the embedding route
Distinguish a staff portal from a customer-facing application. Power BI's secure portal embed requires authenticated, authorised viewers; those viewers generally need Pro or Premium Per User licences unless both the report and semantic model are on qualifying capacity. Verify the customer-facing route separately during the trial.
Tableau's Embedding API supports connected-app authentication. Tableau site settings and connected-app domain allowlists are separate controls; with connected-app direct trust, the connected-app allowlist governs its embed location. Check the actual sign-in flow in the browsers the audience uses.
Looker distinguishes private embedding, which requires a Looker login, from signed embedding through an application.
Place the trial view in its intended host page. Check that an authorised user can open it, an unauthorised user cannot, and required filters and interactions work. Inspect whether users can download data from the embedded view; embedding alone does not settle the export requirement.
Record the conditions of a pass
For each route, save the user role, edition or capacity, relevant settings, host environment, output inspected and limitations found. Mark a requirement passed only for the configuration demonstrated. If customer authentication, scheduled delivery or a restricted-user case could not be tried, record it as unverified before purchase.
