This is expected behavior in Apsona. While IF / ELSE / ENDIF conditional logic is evaluated correctly during the merge, Apsona does not fully support parsing these conditional directives when they are used inside sublists. During template parsing, any fields referenced within the conditional statements are still detected as regular merge fields, causing them to appear in the top-level field mapping even though they belong to the sublist.
Although these fields appear in the top-level mapping, they do not affect the merge output and can safely be left as-is. The merge will still evaluate the conditions correctly and produce the expected result.
For customers who want cleaner field mappings, the recommended approach is to move the conditional logic into a Calculated Field in the sublist report instead of using IF / ELSE / ENDIF tags in the Word template. The template can then reference only the calculated field, which appears correctly within the sublist record group mapping and keeps the template simpler and easier to maintain.
When using conditional logic within sublists, remember that IF / ELSE / ENDIF directives are not fully supported during template parsing. For complex conditions, implementing the logic in a calculated field provides a more predictable and maintainable solution.