iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The JCars project’s workflow starts by cleaning and validating the sales records, not by building charts. Its author describes using Power Query to standardize inconsistent fields and currencies, checking recorded revenue against a stated calculation, then modeling sales and location data for explicit DAX measures and a two-page executive report. The results are the author’s project findings—not audited JCars company performance.
Why the data needs work before dashboarding
The project author describes a flat-file export with inconsistent text and dates, percentages stored as text, mixed currencies, and questionable recorded revenue. These problems can make an attractive dashboard misleading: a visual will summarize whatever values reach the model, including errors and inconsistent units.
The author’s examples include converting the Excel serial date 46066 and changing a text percentage such as “7%” into the decimal 0.07. These are examples from the walkthrough, not independently inspected source records. The practical sequence is to profile the columns, decide what each field should mean and look like, then transform the data before relying on its totals.
Recommended Free Tools
How the project cleans the CSV in Power Query
The author describes using Power Query to standardize text and dates, convert percentage strings to decimals, parse currency suffixes, handle missing or error text, and convert USD, ZAR, and EUR amounts to a KES baseline using static exchange rates.
#1 Best Overall
Standardize types and representations
- Normalize inconsistent text so equivalent categories do not remain separate because of formatting differences.
- Convert date values into a consistent date type rather than mixing text and serial representations.
- Parse percentages as numeric decimals: the author’s “7%” example becomes 0.07.
- Interpret currency suffixes before converting amounts. A value without a known currency or an unparseable value should be treated as a data-quality exception, not silently assumed to be KES.
Handle missing and invalid values deliberately
The walkthrough says missing and error text is handled, but does not establish a universal imputation rule. In practice, distinguish a genuinely missing value from a conversion error or a business value of zero. Record which rows are changed, excluded, or held for review; replacing all three cases with zero can distort revenue and cost measures.
Make currency conversion assumptions visible
Converting USD, ZAR, and EUR to KES provides a common reporting baseline in the described project. The author says the rates are static; the rates themselves and their effective dates are not established here. A static conversion is therefore an assumption of this project, not evidence of transaction-date exchange rates or a current valuation. Preserve the original amount and currency alongside the converted amount when possible so the transformation can be traced.
How the project checks recorded revenue
Rather than trusting the source’s recorded revenue field, the author compares it with this project-specific rule:
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
(Unit Price * (1 - Discount)) * Units Sold
The author reports that the recorded column contained discrepancies, missing discounts, and negative error values, and uses calculated revenue for the analysis. That formula is the project’s chosen validation rule; it is not established as the right accounting definition for every business. For example, business rules may treat discounts, returns, taxes, or fees differently.
Use the calculation as a check, not an unquestioned replacement
For a row with valid price, discount, and quantity, compare the calculated result with recorded revenue and investigate material differences. Check whether the discount is represented as a decimal, whether units sold is the intended quantity, and whether both revenue fields use the same currency and include the same adjustments. If an input is missing or invalid, flag the row instead of presenting a precise-looking calculated value as reliable.
This approach makes data quality visible: a mismatch is a signal to investigate definitions or source entry, not proof by itself of which number is correct. The project author attributes the discrepancies to manual point-of-sale revenue entry; that is a reported project interpretation, not an independently verified account of JCars’ operations.
How the data model supports executive reporting
The author describes a star schema with a sales fact table and location and vehicle dimensions, joined through one-to-many relationships with single-direction filtering. The fact table holds the sales records being summarized; dimensions provide the descriptive context, such as branch or vehicle, used to group and filter them.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →This structure separates transaction-level values from descriptive attributes and gives report filters a clearer path through the model. Confirm that each dimension key is unique on its “one” side and that the fact table’s keys map to the intended dimension records. The source material does not establish the precise keys or table definitions used in the project.
Why explicit DAX measures matter
The project uses explicit DAX measures for total sales revenue, total costs, gross profit, and gross profit margin instead of relying on implicit aggregations. Explicit measures make the intended business calculation visible and reusable across visuals. The exact DAX expressions and the treatment of costs are not established in the project description, so the measure names alone should not be mistaken for fully specified accounting definitions.
Rank #4
Before publishing, define what counts as revenue and cost, whether returns are included, and how margin behaves when revenue is zero or unavailable. Those choices affect the result as much as the visual design does.
How the two-page report connects summary and logistics detail
Executive summary
The described first page brings together KPI and trend visuals for a high-level view of performance. Its purpose is to let an executive see the selected measures and their movement without beginning in a row-level export.
Logistics analysis through drill-through
The second page is a logistics analysis page reached through drill-through. It lets a reader select a branch from the summary and investigate vehicle logistics cost and customer ratings for that branch. This connects a high-level result to a more specific question: where might logistics costs or customer feedback be contributing to the pattern?
Drill-through is useful only when the selected branch context is carried into the detail page and the measures there use consistent definitions. The project description explains the intended interaction, but does not provide enough detail to verify the report file or its exact configuration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the author reports—and what the figures do not prove
The title-matching author reports three management insights: heavy vehicle types reduced gross margins because of logistics costs, manual point-of-sale revenue entry caused accounting discrepancies, and currency exposure supported standardizing regional price lists. These are interpretations from the author’s project analysis, not independently confirmed company facts.
Other public JCars project write-ups report incompatible results. Kelvin Warui’s 2026 article reports 276 transaction records across 32 columns and 255 retained records after cleaning. Gloria Adhiambo Awinja’s 2026 article reports KES 415.5 million in gross profit across 276 analyzed order lines. Another separate project article reports negative gross profit. These are outputs reported by different authors, not audited statistics about JCars, and they should not be combined into one performance story.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The disagreement matters because different choices about row interpretation, retained records, repeated IDs, missing values, currency conversion, revenue and cost formulas, and returns can materially change a dashboard. A separate JCars write-up describes one recorded vehicle order line per row and notes that a line can contain multiple units; that observation is specific to that article and should not be assumed to define the title-matching project. In any such model, order-line counts and vehicle-unit totals are different measures.
Quick Recap
How to read or reproduce the project responsibly
- Attribute the cleaning choices, formula, model, dashboard design, and reported insights to the project author.
- Do not present the project’s findings or figures from other JCars write-ups as verified company performance.
- Keep the transformation assumptions visible, especially static exchange rates and the selected revenue rule.
- Check the data grain before counting records, order lines, or units.
- Compare project outputs only when the underlying files and definitions are aligned. The available descriptions do not establish a definitive ranking of implementations.
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.
