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) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Problem understanding custom fields
Pages: [1]

Author Topic: Problem understanding custom fields  (Read 1295 times)

jddarling

  • Guest
Problem understanding custom fields
March 16, 2008, 10:05:10 pm
I've added a custom field called 'attendee name' so that when people sign up for events, they have to include the attendees name - it's a required field. What I don't understand is why that field also shows up when I create an event, as a required field. I only want it to be a field that a customer fills out, not a field that I have to fill out when creating the event. I realize I'm just missing something - can't figure out what it is.

Yashodha Chaku

  • Forum Godess / God
  • Ask me questions
  • *****
  • Posts: 755
  • Karma: 57
    • CiviCRM
Re: Problem understanding custom fields
March 16, 2008, 10:22:11 pm
While creating Custom Data Group for custom field 'attendee name', set "Used For" as Participants instead of Events.

hth
-yashodha
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

jddarling

  • Guest
Re: Problem understanding custom fields
March 16, 2008, 10:45:15 pm
Thanks man! It would be nice to be able to just change/edit that instead of having to create a new one. But it worked great, I really appreciate the help.

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Problem understanding custom fields
March 16, 2008, 11:31:21 pm
There are too many complications/ validations involved if you keep "Used For" editable.  Hence it is not editable.

kurund
Found this reply helpful? Support CiviCRM

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Problem understanding custom fields

This forum was archived on 2017-11-26.