The JCars Power BI project describes a practical sequence: clean inconsistent sales and logistics data in Power Query, test recorded revenue against an explicit formula, model the cleaned data as a star schema, define DAX measures, and connect an executive summary to branch-level logistics detail with drill-through. Its reported insights belong to the project author; they are not independently verified JCars performance figures.
What the JCars dashboard project set out to do
The project author, Elvis, describes starting with a raw CSV export containing inconsistent text and dates, percentages stored as text, amounts in multiple currencies, and questionable recorded revenue. The aim was not simply to make charts: it was to create a usable model and a report that could move from high-level sales indicators to a selected branch’s logistics details.
As an Amazon Associate I earn from qualifying purchases.
That order matters. A polished visual cannot resolve a misread date, an unparsed currency value, or a revenue field that does not agree with its underlying inputs. In the author’s account, data preparation and validation came before reporting.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How the author cleaned the CSV in Power Query
The walkthrough describes standardizing text and dates, converting percentage strings to decimals, parsing currency suffixes, handling missing or error text, and converting USD, ZAR, and EUR amounts to a KES baseline using static exchange rates. The author gives Excel serial date 46066 and “7%” converted to 0.07 as examples; these are examples from the article, not independently inspected source records.
#1 Best Overall
Make types and conversions explicit
- Dates: Convert source values to a consistent date type, checking how numeric serials are interpreted rather than assuming they are already readable dates.
- Percentages: Convert text such as “7%” to the decimal 0.07 so calculations can use the value correctly.
- Currency: Parse currency indicators and normalize amounts to the project’s KES baseline. Because the author describes static exchange rates, the resulting values depend on those chosen rates; they should not be read as time-sensitive market conversions.
- Missing and error values: Identify how blanks and error text are handled instead of allowing them to silently distort calculations or disappear during aggregation.
The article does not provide independently verified source rows or a reproducible Power Query script in the material available here, so its examples explain the approach rather than establish the exact contents of the original CSV.
How the project checked revenue instead of trusting the recorded field
Elvis says the recorded revenue column contained discrepancies, missing discounts, and negative error values. The project compared the recorded field with a calculated value using this rule:
(Unit Price * (1 - Discount)) * Units Sold
This is the project’s chosen validation rule, not a universal accounting definition. A business may need to account for returns, taxes, fees, or other rules differently. The key method is to compare the source revenue with a calculation whose inputs and assumptions are visible, then investigate mismatches rather than treating either value as automatically correct.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #2
The author’s stated finding was that manual point-of-sale revenue entry caused accounting discrepancies. That is a reported project insight, not an independently verified statement about JCars’ operations.
How the data model and DAX measures fit together
The author describes a star schema with a sales fact table and location and vehicle dimensions, linked through one-to-many relationships with single-direction filtering. This separates transactional records from descriptive branch and vehicle attributes, making the model easier to use across report visuals.
The project uses explicit DAX measures for total sales revenue, total costs, gross profit, and gross profit margin. Explicit measures make the calculation used by a visual intentional and reusable, rather than relying on an implicit aggregation of a column. The article’s account does not establish the precise definitions or formulas for all four measures, so those should not be inferred from their names alone.
Keep the data grain in view
A separate JCars analysis describes one recorded vehicle order line per row and notes that a line can include multiple units. That observation is a useful modeling caution, but it is not established as the grain of Elvis’s specific project. When working with a dataset like this, distinguish order-line counts from vehicle-unit totals and define which one each KPI represents.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHow the report connects executive KPIs to logistics detail
The described report has two pages: an executive summary with KPI and trend visuals, and a logistics analysis page reached through drill-through. A reader can select a branch in the summary and inspect vehicle logistics cost and customer ratings for that branch on the detail page.
This structure serves two different questions without making the overview carry every operational detail: how the business is trending, and what logistics-related values appear for a particular branch. Drill-through is useful only if the field used to carry the branch context is consistent across the model and the destination page; otherwise the detail view may not reflect the selection as expected.
Rank #4
What management insights the project reports—and what they establish
Elvis reports three findings: heavy vehicle types reduced gross margins because of logistics costs; manual point-of-sale revenue entry contributed to accounting discrepancies; and currency exposure supported standardizing regional price lists. These are the project’s reported interpretations of its analysis, not audited company facts or independently confirmed JCars outcomes.
The practical value of such findings depends on the definitions behind them: how gross margin and logistics cost were calculated, which records were retained, and how currencies and exceptions were treated. Those assumptions should accompany any attempt to reuse the conclusions for business decisions.
Recommended Free Tools
Why public JCars project totals should not be combined
Separate public analyses report materially different data handling and outcomes. Kelvin Warui’s 2026 project article reports 276 transaction records and 32 columns, with 255 records retained after cleaning. Gloria Adhiambo Awinja’s 2026 article reports KES 415.5 million gross profit across 276 analyzed order lines. Another project article reports negative gross profit. These are outputs reported by different authors, not independent JCars statistics.
The disagreement is a reason to examine method, not to select a number as the definitive result. The analyses cannot be treated as directly comparable without the original files and definitions. Relevant differences include:
- Whether the row represents a transaction, order line, or individual vehicle unit.
- How repeated IDs, missing values, and records excluded during cleaning were handled.
- Which exchange rates and conversion assumptions were used.
- How revenue and cost were defined, including treatment of returns and discounts.
- Whether a figure is a project calculation or an independently verified company measure.
The underlying CSV, Power BI files, cleaning code, exchange-rate assumptions, and measures were not independently inspected or reproduced for this article. No independent organization-published JCars performance statistic is established by the cited project write-ups.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
