0

How would I set up a registration form where participants may enter their employers data alongside their own. We hardly don't have individuals signing up for our events as private people. They always participate as representatives for their organizations. So we need a registration form holding an organization profile besides the person profile.

Civi's signon form doesn't seem to allow organization based profiles and Drupal's webform with civi integration would register both contacts to the event in question. And the latter has some more downsides (See Webform event registration: Custom data of events loaded by url and Webform event registration: Show event data by token)

What did I miss? Any best practices?

  • You say "Drupal's webform with civi integration would register both contacts to the event in question". I don't think this needs to be true. You can specify which contact on the webform gets registered for the event – petednz - fuzion Feb 11 '17 at 21:09
  • Oh boy, that would be cool. And do you know if the other contacts gonna be related? I'll have a look next days. – nielo Feb 12 '17 at 13:27
  • cool. will add as an answer then. – petednz - fuzion Feb 12 '17 at 18:58
0

You say "Drupal's webform with civi integration would register both contacts to the event in question". I don't think this needs to be true. You can specify which contact on the webform gets registered for the event

  • Webform does it all. Maybe a bit confusing thanks to the mass of options. – nielo Feb 16 '17 at 10:41
0

Part of the question is figuring out what you would like the end result to be. What should the employer data look like in Civi? The 'obvious' answer of an org record for the employer with an employer/employee relationship may not really be best.

There are many aspects to consider: If you have multiple registrations from the same employer, you don't want duplicate org records but do you want them all updating the same record? Users may use different forms of the company name, or may use the same name to describe different parts/locations of the company. De-dupe rules help avoid duplicates but you can end up with updates being applied blindly - ie the user does not know what data you already have and overwrites it. On the other hand exposing your list of organisations and relevant data for them to select from has privacy concerns.

If you want to answer questions about who has attended your past events, then pulling in the employer from a relationship will give bad data if the participant has changed employer since the event. You could try to look at the past relationships to find the applicable one at the time of the event but that gets awkward.

So... as often, there's no one answer that fits everyone. One simple approach is to add custom fields for the employer on the participant registration profile. If you really need a linked org record, you can create one manually.

  • Hmm, do your concerns not apply to all public forms containing organization data? Civi profiles for organizations used in the public wild have to deal with those problems too, don't they? Anyway I read this as: There's no core implementation, do it yourself. Right? – nielo Dec 14 '16 at 14:38
  • 1
    Nielo - you're right that those issues relate to any way that you take in organization data, not just profiles. I guess that's a fair reading :-) If someone figures out a good general design it might one day make its way into core or an extension. Hopefully you'll get a few other responses. – Aidan Dec 14 '16 at 16:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.