Skip to content

GitLab

Closed
Created by kainuk@kainuk

Custom Field of type Integer that uses Radio Buttons as Input Type in combination with search range scrambles Case Report Search

Overview

https://civicrm.stackexchange.com/questions/38562/why-does-my-delete-case-action-in-the-case-search-report-not-work

Reproduction steps to create the testcase

  1. Create a Custom Field on Cases of the type Integer
  2. Start with display type 'Single Input Line'
  3. Enable 'Is this Field Searchable?'
  4. Now 'Search by Range' becomes visible.
  5. Change the display type to Radio Buttons.
  6. Add some Option Values and save the field.

Remark, some interface magic is required to create this situation. I think its more done by accident, than by intent.

Current behaviour

The behaviour is now as described in https://civicrm.stackexchange.com/questions/38562/why-does-my-delete-case-action-in-the-case-search-report-not-work .

Expected behaviour

The Case Search report should just work

Environment information

This issue can be reproduced on 5.34.alpha1 or on the https://dmaster.demo.civicrm.org

Comments

#337 (closed) contains a discussion if the combination 'Radio Buttons' and 'Search by Range' should be allowed.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information