CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions »
  • CiviContribute Suggestions »
  • Why do we hide the Check number field?
Pages: [1]

Author Topic: Why do we hide the Check number field?  (Read 868 times)

joanne

  • Administrator
  • Ask me questions
  • *****
  • Posts: 852
  • Karma: 83
  • CiviCRM version: 4.4.16
  • CMS version: Drupal 7
Why do we hide the Check number field?
July 07, 2014, 08:11:57 am
I would like to add my support to doing something about https://issues.civicrm.org/jira/browse/CRM-14761.

I think CiviCRM is being too controlling by only having the cheque number field display when the payment instrument is Cheque.

If someone can't work out when that field needs data entered into it and when it should left empty then personally I would not want want them entering payments into CiviCRM.

I am interested in this as we sometimes receive money orders.  A money order is different from a cheque in that it can't be "stopped" by the person who sent it in  and it can't bounce, so we have a different payment instrument for them.

However, they share the feature of having a number like a cheque number so I would really like to be able to have the money order number entered into the cheque number field.  (And yes, the people who enter payments into my CiviCRM would be able to cope with entering the money order number into a field labelled cheque number.)
« Last Edit: July 11, 2014, 07:15:18 pm by joanne »

joanne

  • Administrator
  • Ask me questions
  • *****
  • Posts: 852
  • Karma: 83
  • CiviCRM version: 4.4.16
  • CMS version: Drupal 7
Re: Why do we hide the Check number field?
July 11, 2014, 07:47:54 pm
At the risk of adding this to the ever growing list of 'things I will work on when I have enough time to learn how to do them', what would a solution to this involve?

Current situation is that civicrm_contribution.check_number already exists but it only becomes visible for the reserved payment_instrument_id =  4  (check/cheque) .

For me it would be good enough if that field was always visible and always labelled 'check number', but I imagine some people would object to that ( obviously  - otherwise why is it mostly hidden now)

So what would constitute an acceptable solution.  I am not looking for the absolute best solution rather looking for one that would be accepted into core (which could be the same thing I realise).
  • visible for all custom payment instruments and always labelled "check number"
  • visible for all custom payment instruments  and always labelled "XXX number"  where XXX is the name of the payment instrument
  • checkbox selectable for  custom payment instruments and always labelled "check number"
  • checkbox selectable for custom payment instruments  and always labelled "XXX number"  where XXX is the name of the payment instrument
  • checkbox selectable for custom payment instruments  and with a custom label
I am not committing to doing this - there 10 things already on my list, I don't have the skills to do any of them and documentation and the forum already occupy all my spare time, but I am interested in knowing what would be the standard to aim for.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions »
  • CiviContribute Suggestions »
  • Why do we hide the Check number field?

This forum was archived on 2017-11-26.