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) »
  • Importing old events -- getting around price-set restrictions
Pages: [1]

Author Topic: Importing old events -- getting around price-set restrictions  (Read 635 times)

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Importing old events -- getting around price-set restrictions
October 22, 2010, 05:00:07 pm
Hi folks. I wonder if anyone has come up against this:
I have a whole pile of old event registrations to import. I'm pretty good with the APIs and writing import scripts, but this one stumped me. Not having used civievent until now, I find the price-set thing difficult to manage. See, these old events were all on a sliding scale, so the amount people paid was pretty random. So I don't want or need price-sets to be associated with these events. I just want to create the old event in CiviCRM, then use my import script to add participants, and record how much they paid. Simple right? And yet, why is this not at all simple? ???
When I go to create the old event, Civi asks me if it was a paid event. It was, so I say yes. If I said no, then there would be no way to associate contributions with the event, I take it. But now it forces me to add at least one fixed-price option or price set, which there is no reason for me to do in this case, but, not having any choice, I do it - I add a fixed price of $600. Then I try adding my buddy "Joe Tester" to the event. It forces me to choose $600 as the amount he paid, but then immediately after, the civicontribute fieldset gives me a blank textfield where I can enter the actual amount that he paid. That's all I wanted in the first place. So I put in $25.
CiviCRM now glibly reports to me that Joe's event fee was $600 (and only if I click an extra level deep and load the actual contribution record will it tell me that the "actual" amount was $25). That's _not_ useful!
If anyone has any advice for a better approach to this, I'd really love to hear it.
Try asking your question on the new CiviCRM help site.

qjensen

  • I post frequently
  • ***
  • Posts: 141
  • Karma: 11
    • Scaled Solutions
  • CiviCRM version: 4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Re: Importing old events -- getting around price-set restrictions
October 26, 2010, 03:28:25 pm
Is it just the fact that the UI buries that contribution record one level down that is bothersome for you? If so, you could tweak the display to show the contribution on the main page using a custom form.
Quint Jensen
Web Developer
Scaled Solutions
--" Remove the 'I want you to like me' notes from your forehead and place them where they truly will do the most good -- on your mirror!" Author Unknown

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Importing old events -- getting around price-set restrictions

This forum was archived on 2017-11-26.