Build a fresh set of related and conditional fields without copying values from a visible report. For each request, identify the receiving business object and work outward through its relationships. A lookup can consume a selected instance; an expression can consume a Boolean or a count. Save the dependency before the field that refers to it.
Inspect a no-match result as carefully as an ordinary value. A worker without approved time off has no latest request, while a count of approved requests is zero. Those answers should not be swapped. A dependency must lead back to source data rather than back to itself. Keep field names descriptive enough that another analyst can trace the calculation without opening every definition.