Groundwire / EventbriteSync

Salesforce.com-based tool that imports people and event registrations from Eventbrite into Salesforce.
16 stars 10 forks source link

Option to create registration opps for the company rather than the individual #10

Open groundwired opened 12 years ago

groundwired commented 12 years ago

If the company field is filled in, people might want opps to be created for the company rather than the individual. We are currently not setting the Account Id for the opps we create.

tet3 commented 12 years ago

We would definitely like to have Opportunities attached to the Account. Why do you say "rather than" the contact? We use neither NPSP or Groundwire template, and unaffiliated Contacts are handled with a bucket Account in our instance. I'm seeing our Opportunity.Main_Contact__c Lookup field to Contact populated on the Opportunity (is that because our dev was prescient enough to use the same field name you do? Woot!), and the Contact also gets a Primary Contact Role. Why would completing the Account lookup field be instead of, not in addition to, these items?

Also, you write "If the company field is filled in," and I think you're talking about the EB Company field. We might actually prefer using the matched Contact's Account in all cases rather than trying to match the Eventbrite Company to Salesforce Account.

groundwired commented 12 years ago

Hey thanks for the input. Here's what I meant - our clients and the NPSP use the Account Id field to indicate whether money is from a person or from an employer. If it is from the person, we do not set the Account Id at all, so we would want to fill Account Id if and only if the company pays. But you raise a great point, in that it should not matter whether the EB Company field is filled in, only whether an account connection exists and the admin indicates they want this. If we do the feature, it will be box that says "Attach opportunities to purchaser's account" or some such thing.

Sadly at this point we can't always tell who the purchaser is from the API data (in the case that you request names for each attendee). I am talking to Eventbrite about this - hopefully will get it fixed.

groundwired commented 12 years ago

Changed this to high priority to reflect the fact that it would probably be required to support opps with 1-to-1 model.