Reports reliability

[tpmtpm56]

Flare's Reports: Can I rely on them?
I inherited a large and very messy project and want to remove anything not used, for example unused conditions.
I create a Report and in the category "Condition Tags" select only "Undefined Condition Tags" and "Unused Condition Tags".
The generated Report results show me conditions that seemingly appear from nowhere: They'rre listed in the Report, but are nowhere to be found in the project - neither in Target Editor > Conditional Text, nor in Project Organizer > Conditional Text.
What's their source, how can I find them in their location inside Flare, and how can I get rid of them?
Thanks.

[ChoccieMuffin]

It's possible that there are some conditions included in the code for some topics that don't have corresponding conditions in the condition tag set (but I couldn't promise).

So search in your topics in the source code for whatever the condition is, for example "MadCap:conditions="Primary.QUESTION" (without the quote marks).

No idea if it'll work but worth a try.

[doc_guy]

If you have Analyzer (or Flare 2018, because these features are now built into Flare), you can find these references to undefined styles or undefined conditions, and remove them directly in Analyzer (or from the Flare Analysis tab in Flare 2018).

[tpmtpm56]

Thanks; these rogue condition tags don't seem to be doing any harm (but frustrated that yet another layer of unintuitive Flare complexity reveals itself: where do these things come from? They're like mushrooms; various elements seem to pop up all over the place), so manual search it will be until I upgrade to 2018, and then try with Analyzer.

[NorthEast]

If you're getting odd results in project analysis (analyzer) or reports, then close your project and delete the Analyzer folder.

[tpmtpm56]

Yep, thanks Dave.
Still, I find report results bizarre, and in many cases not very revealing. I've learned to take them with a grain of salt.