DITA map filtering not applied when publishing to WebHelp Responsive

[lylybrown]

Hi everyone,
I'm currently working on a DITA project and having trouble publishing to WebHelp Responsive. I'm using analytics properties to filter specific content within topics, and the filtering works correctly when I preview individual topics or generate other outputs like PDFs. However, when I publish the entire DITA map to WebHelp Responsive, some of the filtered content still appears in the output.
I've checked the DITAVAL file and ensured it's referenced in the conversion script, but the results are inconsistent when building the entire document. Are there any specific settings or common errors that could cause the filtering rules to be ignored during WebHelp publishing?
Thanks!

[julien_lacour]

Hello,

Have you tried to use the Validate and Check for Completeness tool available in the DITA Maps Manager?
You can use it to control the ditamap integrity against a ditaval, you may get errors/warnings that could explain why some filtered topics are still displayed in the output.
Also if you generate different outputs, using different filters, in the same output directory, make sure to run the scenario with the 'clean.output' parameter enabled. The extra files can be leftovers from a previous run.

Regards,
Julien

[swarthyavoo]

You might want to double-check that the DITAVAL file is actually included in the WebHelp Responsive transformation scenario, not just referenced in the conversion script. In some setups the filtering works for topic previews or PDF builds because the scenario explicitly loads the DITAVAL file, but the WebHelp build may use a different configuration. Also verify that the profiling/conditional attributes used in your topics match exactly with those defined in the DITAVAL file, and try doing a full clean build to clear any cached output. Sometimes cached content can cause filtered elements to still appear in the final WebHelp output.