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) »
  • Developer Discussion »
  • APIs and Hooks (Moderator: Donald Lobo) »
  • Custom Fields names when referencing from payment processor
Pages: [1]

Author Topic: Custom Fields names when referencing from payment processor  (Read 525 times)

angelog

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 3.4
  • CMS version: Drupal
  • MySQL version: 5.5
  • PHP version: 5.3
Custom Fields names when referencing from payment processor
October 27, 2011, 06:50:28 am
I am relatively new to Civi development. I am developing a payment processor and referencing a custom field that needs to be passed on to the external payment processor. In my development Civi system, based on the provided sample data, the new created custom field is named as custom_53.

I would appreciate any help or advice on how I might be able to control the name of the custom field. My issue is that when I port my processor to difference environment, that is, customer's test and live environment, and setup the custom field, the internal reference to the field will be different in each environment. I would like to be able insulate the code from these name changes without changing my code each time.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion »
  • APIs and Hooks (Moderator: Donald Lobo) »
  • Custom Fields names when referencing from payment processor

This forum was archived on 2017-11-26.