{"action":"closed","issue":{"url":"https://api.github.com/repos/givingforum/givingforum/issues/108","labels_url":"https://api.github.com/repos/givingforum/givingforum/issues/108/labels{/name}","comments_url":"https://api.github.com/repos/givingforum/givingforum/issues/108/comments","events_url":"https://api.github.com/repos/givingforum/givingforum/issues/108/events","html_url":"https://github.com/givingforum/givingforum/issues/108","id":28995988,"number":108,"title":"Event Registration detail is not mapped to Salesforce","user":{"login":"wcorkill","id":4803610,"avatar_url":"https://avatars.githubusercontent.com/u/4803610?v=3","gravatar_id":"","url":"https://api.github.com/users/wcorkill","html_url":"https://github.com/wcorkill","followers_url":"https://api.github.com/users/wcorkill/followers","following_url":"https://api.github.com/users/wcorkill/following{/other_user}","gists_url":"https://api.github.com/users/wcorkill/gists{/gist_id}","starred_url":"https://api.github.com/users/wcorkill/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wcorkill/subscriptions","organizations_url":"https://api.github.com/users/wcorkill/orgs","repos_url":"https://api.github.com/users/wcorkill/repos","events_url":"https://api.github.com/users/wcorkill/events{/privacy}","received_events_url":"https://api.github.com/users/wcorkill/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/givingforum/givingforum/labels/Vote%20Required","name":"Vote Required","color":"eb6420"}],"state":"closed","locked":false,"assignee":{"login":"wcorkill","id":4803610,"avatar_url":"https://avatars.githubusercontent.com/u/4803610?v=3","gravatar_id":"","url":"https://api.github.com/users/wcorkill","html_url":"https://github.com/wcorkill","followers_url":"https://api.github.com/users/wcorkill/followers","following_url":"https://api.github.com/users/wcorkill/following{/other_user}","gists_url":"https://api.github.com/users/wcorkill/gists{/gist_id}","starred_url":"https://api.github.com/users/wcorkill/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wcorkill/subscriptions","organizations_url":"https://api.github.com/users/wcorkill/orgs","repos_url":"https://api.github.com/users/wcorkill/repos","events_url":"https://api.github.com/users/wcorkill/events{/privacy}","received_events_url":"https://api.github.com/users/wcorkill/received_events","type":"User","site_admin":false},"milestone":null,"comments":14,"created_at":"2014-03-07T20:29:59Z","updated_at":"2015-07-27T21:25:05Z","closed_at":"2015-07-27T21:25:05Z","body":"Currently event registration data is mapped to Opportunities and Campaign Members.\r\nOpportunities track the Order Total and person who placed the order and Campaign Members are linked to the Opportunity to show which registrants are tied to that order.  \r\n\r\nThe issue with the campaign member record does not track the fee or product selected during registration.  For Complex events that have multiple products and for orders with multiple registrants, there is not way to produce a break down of who has chosen what event product or how much thier individual registration is in Salesforce.  \r\n\r\nTo fix this issue I have 3 proposed solutions outlined below.  after reviewing these options with the Salesforce Working group, the group recommended that we pursue getting an estimate on options 2 and 3.\r\n\r\nTHE NEED: To generate line item detail invoices for event registrations that includes detailed information about products and total amount for each registrant.\r\n \r\n*Solution #1\r\n \r\n**Add 2 new fields, use existing field\r\n- On Campaign Members, use existing FEE field; Create field to capture PRODUCT SKU and PRODUCT DESCRIPTION\r\n- Pulled from the line item in the Drupal order\r\n- Current mappings only bring event registrant from each line item to the campaign member record\r\n \r\n**Who gets the work done?\r\n- RAs adds fields to SF (or add to Basic Package)\r\n- ThinkShout fixes mappings\r\n \r\n**Potential drawbacks\r\n- Tracking monetary portion outside of the Opportunity record\r\n- Possible reporting issues\r\n- May not be smartest long-term solution (deceiving in that it is cheapest and easiest solution)\r\n- RA cannot edit Event Registration mappings, still managed in code rather than using existing Salesforce Mappings function.\r\n \r\n*Solution #2\r\n \r\n**New Opportunity records for each line item from Drupal\r\n- What happens now – each Drupal Order generates an Opportunity record\r\n- Opportunities would be equal to Drupal line items\r\n \r\n**Who gets the work done?\r\n- ThinkShout creates new mappings\r\n- RAs add new fields (or add to Basic Package)\r\n \r\n**Potential drawbacks\r\n- Does not mirror the complete order/line item data structure currently in Drupal\r\n \r\n***Other considerations\r\n- If we map the Drupal Order Number to the existing Basic Package Order Number field in the Opportunity record, you could group by this field in a summary or matrix report (lowers significance of potential drawback noted above)\r\n- Lower complexity than Solution #3\r\n- Overcomes drawback from Solution #1\r\n- Products currently use a similar design as this and mappings can be edited/modified by RA, Event registrations cannot be edited currently and this should allow mappings to be modified and updated by RA\r\n\r\n\r\n*Solution #3\r\n \r\n**Implement Opportunity Products\r\n- Closest we'll get to mirroring current data structure in Drupal\r\n- Drupal Order is equal to Opportunity\r\n- Each Drupal Line Item is mapped to an Opportunity Product (custom object, native to SF, related to Opportunity object)\r\n- Campaign Members would be linked to the Opportunity Product instead of the Opportunity\r\n \r\n**Who gets the work done?\r\n- ThinkShout\r\n- Brian Pickett\r\n \r\n**Potential drawbacks\r\n- High complexity\r\n- Cost – both in terms of ThinkShout time and consulting time from Brian Pickett\r\n \r\n***Other considerations\r\n- Vast majority of third-party SF native Accounting solutions use Opportunity Products\r\n- SF mappings in Drupal would be consistent across all orders (Events, Products)\r\n- Events and Products (publications etc) are currently managed differently\r\n"}}