How do you handle missing data in a report design?

• A. Ignore missing data and proceed.
• B. Provide default values, use null handling logic, or restrict data via prompts/filters to avoid blanks.
• C. Manually remove any records with missing data.
• D. Only use data with complete fields; otherwise error.

Answer: (B)

Handling missing data in a report design means deciding what to show when a field has no value and how calculations should behave so results stay meaningful and reliable. The best approach combines practical options: provide default values, use null handling logic, or restrict data with prompts or filters to avoid blanks.

Using default values puts a defined placeholder in place (for example, Unknown or 0) so the row remains part of totals, charts, and summaries. Null handling logic defines precisely what happens when a value is missing—substitute a value, ignore the null in certain calculations, or carry forward a non-null value. In practice, report tools offer functions to coalesce or replace nulls with sensible substitutes, keeping calculations stable. Restricting data with prompts or filters helps avoid blanks by pulling only records that have the required fields, ensuring the outputs aren’t skewed by missing information.

These strategies preserve data integrity and readability, prevent misinterpretation, and keep the report usable across scenarios with incomplete data. Ignoring missing data can distort results by treating blanks inconsistently. Manually removing records isn’t scalable and can introduce bias. Requiring complete data and halting when missing makes the report brittle and less flexible for real-world datasets.