Problem Statement
In our BI report, several job-related attributes are placed together on shared conditional rows in the RTF template. Due to the current conditional suppression logic, if either attribute in a paired row has no data, the entire row is suppressed, causing both fields to disappear - even when one field contains valid data.
This behavior leads to incomplete or misleading output where important job attributes are unintentionally hidden from the report.
Current Limitation
- The issue is caused by RTF layout constraints combined with row-level conditional suppression logic
- The template must maintain a single-page, two-column layout for the report
- Under these constraints, attributes cannot currently be separated into independent rows without breaking layout standards
- As a result, this cannot be resolved for launch using the existing RTF structure
Business Impact
- Valid job attributes may not appear in the report, reducing trust in reporting accuracy.
- HR partners and leaders may make talent decisions based on incomplete information.
- Customers have limited ability to modify the delivered template without reintroducing layout or pagination issues
Suggested Enhancements
Explore alternative formatting or architectural approaches that allow independent field display without suppressing adjacent attributes, while still preserving a clean, single-page experience.
Possible approaches to evaluate:
- Separating paired attributes into independent rows with attribute-level suppression
- Adjusting conditional logic at the field level rather than the row level
- Re-architecting the RTF layout (or underlying data structure) to avoid shared conditional rows
- Exploring non-RTF layout techniques that still meet page and column requirements
Expected Benefit
- Each job attribute displays independently based on its own data availablity
- No unintended suppression of valid fields
- More accurate, reliable outputs
- Reduced need for customer workarounds or custom template notifications
