1. Multiple Option IDs in `qtextdisplaycondition`:
   • The backend often uses the first option ID to determine which `reportqtext` to display.
   • In some cases, this may be a “No Photo” option (e.g., ID `3119`) instead of an image, resulting in the basis text not appearing.

1. Fix:
   • Add a fallback in `reportqtext` using this format:

`Text for photo option^|||^Text for fallback (e.g., No Photo)`

• Example:

`Vertel, wat is uw beleving bij Centraal Beheer, wat roept de foto op^|||^Vertel, wat is uw beleving bij Centraal Beheer, wat roept de foto op..`

1. Missing Option IDs After Archiving:
   • If an old photo set is archived, the original option IDs may be removed from the `qtextdisplaycondition`.
   • This leads to broken logic for respondents who selected options from the older set.

1. Fix:
   • Ensure that the `qtextdisplaycondition` for follow-up questions includes both old and new option IDs to cover all possible answer paths.

• The exact backend evaluation logic for `qtextdisplaycondition` can vary and isn't always predictable.
• Defining a fallback ensures the `reportqtext` appears even if an unexpected option ID is evaluated first.

In question ID `374`, the basis text wasn’t appearing despite correct configuration.
The condition included image option IDs and a “No Photo” option (`3119`).
The system evaluated `3119` first, skipping the expected text.
✔️ Solution: Use `^|||^` fallback in `reportqtext` to ensure visibility regardless of option ID.