Explore your results in Power BI (optional)

Open the Power BI project generated by AnalyticsCreator and display the Northwind sales results you checked in SQL. This optional page uses the generated model, relationships and measures.

Have a supported Power BI Desktop installation, the complete generated project folder from Generate your warehouse, pipeline and Power BI project, and the passing results from the warehouse checks. Keep the warehouse unchanged while comparing the results.

Open and refresh the generated project

If Power BI Desktop is not installed, get the latest Power BI Desktop from Microsoft or use its 64-bit installer. Microsoft no longer supports the 32-bit Desktop version, so this tutorial uses 64-bit Desktop. Update an older installation before opening the generated project.
Copy the complete generated Power BI project folder to a short local working path, such as C:\ACNorthwind\ReportReview. Keep the original output intact so later regeneration does not overwrite your report edits. Preserve the folder structure, including the report and semantic-model folders.
Open the recorded .pbip file in Power BI Desktop. The file points to the report and its model; copying that file alone is insufficient. Microsoft also supports opening definition.pbir from the report folder. See Power BI Desktop projects for the file structure.
What you should see: the generated report opens and its model fields are available. A report canvas may still need visuals. If the project or its model is missing, return to the generated-output checks before continuing.
Select File → Options and settings → Data source settings. Inspect the sources used by this project and compare the SQL server and database with your setup record. The connection must use the checked warehouse, NorthwindWarehouse, or your recorded retry destination. Use the credentials that have read access to that warehouse when prompted.
If the generated project points to a different database, correct the deployment's Power BI connection settings and regenerate it using the generation procedure. Then open a fresh working copy of that output. This keeps the project and its generation settings aligned.
Select Home → Refresh and wait for completion. For an import model, this reads current warehouse data into the local model. Resolve a refresh or credential error before comparing figures. Microsoft's Desktop refresh instructions describe this action.

Display and compare net sales

In the Data pane, locate the generated order-line fact and the Net Sales, Units and Order Lines measures defined in Connect Northwind and build the model. Compare the actual generated table names with your setup record. Net Sales sums the discounted, line-rounded amounts; Units sums Quantity; Order Lines counts fact rows.
If a required measure or customer relationship is absent, return to the model and generation steps. Do not replace the generated model with a separate SQL import just to produce the expected number.
In report view, add a Table visual. Add only Net Sales, Units and Order Lines. Keep report, page and visual filters empty, and clear slicer selections. Show full numbers, with two decimal places for net sales and no currency symbol.
What you should see: Net Sales 1,265,793.29, Units 51,317 and Order Lines 2,155, matching the saved SQL results. Use the measures, rather than a count of the amount column or a sum of prices, percentages or identifiers. Microsoft's table visual instructions explain how to add and format fields.
Add a second Table visual containing the generated customer identifier, company name and Net Sales. Use the customer fields related to the order-line fact. Find customer QUICK and compare its net sales with the SQL customer result: 110,277.32.
This answers how much net sales each customer contributed. A company name is a label; the customer identifier distinguishes customers. If every customer shows the overall total, inspect the generated customer relationship and measure before accepting the report. Customers with no sales may be omitted by a visual that hides blank results.
Save the working project with File → Save. Record the project path, warehouse location, refresh time, actual measure names, overall net sales and the QUICK customer check in your setup record. Keep the project folders together when moving or backing up the report.

Your local report is ready when it opens from the generated project, refreshes from the checked warehouse and shows the matching sales results. The PBIP files describe a Power BI report and semantic model; they are not an OLAP database.

If the project or figures do not match

For an opening error, confirm that the complete project folder is present, the path is short and the installed Desktop version supports Power BI projects. Keep the error message and return to the generation checks if a referenced file is missing.
For a connection or refresh error, compare the server, warehouse, account and connection settings with the setup record. A connection to the source Northwind database or the design database is not the deployed warehouse connection.
If SQL checks pass but the report differs, clear all filters and refresh after the completed load. Inspect the generated fact's row count and complete order-line key, its customer relationship, and the selected measures. A relationship that duplicates lines can inflate both units and sales.
If only net sales differs, compare the measure with the agreed calculation: convert the discount to four decimal places, calculate each line from its UnitPrice and Quantity, round each line to two decimals, then sum. Freight is excluded. Correct the model definition, regenerate into a new output folder and repeat the warehouse and report checks.