Including Contribution fields in the Find Participants export?

[CiviTeacher.com]

When I use the Find Participants tool and do an export, if I select ALL fields, at the end are the very useful Contribution fields (total amount, payment instrument) for the actual financial transaction for the event registration.

However, if I attempt to select fields for export and create a field mapping, the Contribution fields are not available, only these are: Individual, Household, Organization, Participant

Is there a way to include these Contribution fields (which are evidently already in the ALL fields export) in the 'select your own' field options?

Is this a bug, or just a feature that has not yet been created?  Estimates to fix/complete?  Thanks.

[qjensen]

Custom searches aren't too difficult to build if you know a little SQL. You could create a custom search that returns the fields you want including the Contribution information.

It would be great to see the contribution field available in the field selection options. I don't know how much work it would be to add that...

[CiviTeacher.com]

I got an estimate of 6 hours by web access.  i'm going to have them go ahead if it can be added to core

[Donald Lobo]

we'll definitely consider this for core for 3.4 / 4.0

depending on the time frame and the number of changes involved, we might be able to add it in a 3.3.x release

lobo

[Eileen]

Hi Lobo / Web Access,

If WebAccess are working on this they may be able to share some insight into the LEFT JOINS query.php constructs when getting contribution fields for a participant query since I presume that they will be using that code?

What  I hit was that with the API you get too many contribution records if you asked for contribution_id to be returned on a participant search - i.e if you have

$params('participant_id') =1
$params('return_contribution.id' =1)
participant_get($params}

then Query.php constructs

FROM civicrm_contact LEFT JOIN civicrm_contribution on contact_id LEFT JOIN civicrm_participan on contact_id & gives as many records back as that contact has contributions.

Ideally it would be

FROM civicrm_contact LEFT JOIN civicrm_participan on contact_id LEFT JOIN participant_payment on payment_id LEFT JOIN civicrm_contribution on contribution_id

[Dwiding]

Hi Lobo,

Trying do eaxctly what thispost is about and cannot.

My client is interested in finding how much it would cost to get this implemented.

Thanks!

Dallas

[Donald Lobo]

I dont think we recd a patch for this. hence it never made it into core

lobo

[Dwiding]

So making do with just exporting the results of Find Particpants from any given event and exporting the primary fields.

Question is, what is the difference in Contact Fields such as Address Info and Custom Fields for Contacts that are used for Registration Profiles?

These custom fields are not exported in the "Export Primary Fields" export option.

Two Examples:

Profile Top of Page Collects(Your Contact Info):
First Name (Indvidual, Exported)
Last Name (Individual, Exported)
Address info (Contact, Exported)
Nick Name (Indvidual, Label on profile says "Badge Name", Exported)
Custom Field "Member County" (Contact, NOT Exported -- Not to be confused with State/County Field - Custom Field)
Particpant Note (Participant, Lable on Profile says "Special Needs", NOT Exported)

Profile Bottom of Page Collects (County Reception - Custom Fields):
Number of Guests (Particpant, Not Exported)
Guest Names (Particpant, Not Exported)

I need to get this straightened out so the site can go live. There over 8000 Contact records with some of this data already populated.

Thanks!

Dallas

[Dwiding]

I forgot to include that in the Primary Fields Export, the following Contribution fields are included:

Contribution Status
Received Date
Payment Instrument
Transaction ID

IS there anyone who can modify the Export Routine so that when selecting fields to export, that at least these 4 Contribution Fileds are included?

The client REALLY wants just one lsiting report and does not want to go through creating several worksheets, then doing a lookup function to combine every thing into one list Which is what I am working on at the moment).

From looking at the Custom Searches, I don't think that will suffice without even more customizations.

Client is intersted in funding this if reasonable.

Thanks in advance!

Dallas

[Donald Lobo]

hey dallas:

adding those 4 fields to the primary export should be relatively easy. can you please file an issue and we'll try to get this done before the next release. should not take too long

thanx

lobo

[Dwiding]

Thank you Lobo!

I have to rework 2 of my custom fields so that they are in the primary field export.

WIll file an issue here shortly.

Best!

Dallas

[petednz]

aaack - does this mean this could have been added back then but didn't just for want of adding a ticket 

can i add the ticket? can i, can i