Normalize Decimal and Binary Storage Units with Microsoft Excel (2027)

A size report combines quantities that use different unit conventions. This Microsoft Excel debugging guide starts with that visible symptom and reduces it to a small, reproducible contract. The goal is to explain why the result is wrong, make one focused correction and preserve the corrected behaviour in a regression check.

Use the exercise for 2027 study or portfolio practice. All records and situations are fictional. Start with basic Microsoft Excel knowledge and a local learning environment. Keep the example small until the original failure, accepted policy and expected output can be explained without opening the implementation.

Recognize the failure

The numeric values are added while their units are ignored. One decimal kilobyte and one binary kibibyte therefore become an unexplained total of two.

Write the symptom down before changing the code or configuration. Separate what was observed from what you suspect. Record the exact input and the operation that produced the result; a statement such as “the totals look odd” is harder to investigate than a fixture whose accepted outcome is explicit.

Agree on the contract

Map each accepted unit to a declared byte factor, normalize each record, and sum bytes. Reject unknown units instead of assuming a factor.

The policy in this exercise is deliberately scoped. A matching implementation must produce the expected structure and types, preserve the supplied fixture, and communicate a defined rejection as a completed outcome. Treat null, zero, empty collections and error objects according to this case rather than merging them into one generic fallback.

Reproduce it with this input

[
  {
    "value": 1,
    "unit": "KB"
  },
  {
    "value": 1,
    "unit": "KiB"
  }
]

Expected outcome:

{
  "bytes": 2024
}

Compare the complete result, including value types and any error category. A correct-looking label is insufficient if the transport value or stored state has a different meaning. Keep this golden fixture unchanged while exploring additional examples so the original failure remains reproducible.

Read the checked reference

The collection includes a complete Python reference and executable checks. Save the text download as reference_checks.py to run it locally. The following function is an excerpt from that file; imports and any helpers such as number, instant or ContractError are defined there. The check runner turns a deliberate contract rejection into the error object shown above.

def mixed_storage_units(records):
    factors = {'KB':1000,'KiB':1024}
    if any(r['unit'] not in factors for r in records):
        raise ContractError('unknown-unit')
    return {'bytes':sum(r['value']*factors[r['unit']] for r in records)}

The Python reference is the behavioural oracle for the small fixture. For this Microsoft Excel article, implement the equivalent behaviour at the raw-data-to-metric boundary. The reference check is not evidence that a separate framework, device, database or distributed system has already been implemented or tested.

Apply the fix in Microsoft Excel

Preserve the raw fixture and record each conversion or exclusion in a separate transformation. State the grain, unit and denominator before charting. Reconcile the tiny example by hand, then make the same meaning visible in tables, labels and filter behaviour.

Convert the fixture into a named table and keep input, calculation and presentation areas separate. Verify that numeric-looking cells are actually numbers before building a summary. Make filters and exclusions visible. Protect the meaning of blank cells rather than replacing every missing value with zero, and reconcile a small manual example before sharing the workbook.

Connect these Microsoft Excel design concerns to the case while reviewing the implementation:

• Structured tables.
• Explicit filter criteria.
• Formula and total reconciliation.

Start with the smallest operation that can return the expected outcome. Add the surrounding interface, request adapter, query or verification job only after that operation is understandable. Observe the input immediately before the boundary and the output immediately after it; this helps identify a conversion or state change introduced by the adapter itself.

Add the regression and a valid control

Combine one KB using a factor of one thousand with one KiB using a factor of one thousand twenty-four. Require two thousand twenty-four bytes.

Compare the cleaned records, the intermediate calculation and the final displayed metric. A chart can conceal a type conversion or denominator change, so retain a reconciliation table until the result is verified. Test a changed filter and an empty selection as separate states.

Preserve these track-specific checks as well:

• A newly added row must enter the intended range.
• A filtered subtotal must have a clear denominator.
• Text-formatted numbers must not disappear silently.

Run the complete reference set from the repository root with python reference_checks.py. Save the actual output with the source revision. When adapting the case, keep the expected result independent of the implementation under test; generating an expected value with the same faulty function would reproduce the defect inside the test.

Explain where this example stops

The exercise uses an explicit convention table. External systems may label quantities ambiguously, so their unit definition must be verified before import.

Document one consequence of the chosen policy and one reasonable alternative. If the product contract changes later, update the explanation and expected result deliberately, then add a case that distinguishes the new meaning from the old one. A passing local fixture should stay attached to its stated assumptions.

Present the investigation in a portfolio

Show the failing observation, the input, the policy decision and the corrected result in that order. Include the focused diff, a valid control, the regression evidence and a short explanation of the boundary you changed. Give another learner the fixture and setup instructions so they can repeat the investigation rather than relying only on a screenshot.

For a useful extension, vary one part of the fixture while keeping the policy fixed. Explain the predicted outcome before running it. If the prediction and observation disagree, record that disagreement as the next investigation instead of silently changing the expected value to match the implementation.

Questions learners ask

Does the sample define the only correct product policy?

It defines this lab's policy. Use the stated boundary notes to compare alternatives, then choose the behaviour your own feature promises. Different policies need distinguishable tests and clear labels.

What has actually been executed?

The shared Python reference runner checks this fixture, its expected output and input preservation. A Microsoft Excel adaptation remains a practical exercise until its own implementation and evidence are added. The collection's verification report records the scope of the checks.

How should I use this while choosing a course?

Use the failure and regression as a concrete discussion point. Browse the current Groot Academy course directory and ask about its current syllabus, learning mode and hands-on exercises. Confirm batch availability directly with the academy.

Consult the official Microsoft Excel documentation for the tools you use, and the Python reference documentation for this case for the illustrated parsing, representation or library behaviour. The 2027 label identifies a study edition rather than a prediction about future releases or hiring.

Continue with Reject a Negative Quantity before Updating State with Microsoft Excel, or explore Normalize Decimal and Binary Storage Units with Power BI. These companion practice guides are part of the 2027 learning collection.