Reporting issue of null

What is the challenge?

• Capability field-status audit view

  • Current Aha! reports return both of these conditions as the same blank/null result:
    1. A field exists on a record but has not been populated.
    2. The field is not configured or available for that record’s workspace.

• This prevents reliable interpretation of reporting data and produces false data-quality findings. Reviewers cannot determine whether a record owner needs to supply data or whether the workspace does not support the field.

• The immediate use case is the Its benefit, estimate, date and other key fields are inconsistent across workspaces. A field-status audit is needed to identify whether each tracked field is populated, blank but available, or unavailable for the record.

• This should be built in if possible as to why data is blank.

What is the impact?

• inconsistent workspace settings can be verified faster

Describe your idea.

• So when different layouts are used, indicate on a report that the field is not on a layout.

•