I'm using NPSP, for the record, and do not have payment allocations enabled. I'll need to be able to filter for close date/ payment date as well, but don't think that'll be an issue. Would love any tips, will do whatever to be able to get the results I need! Previous attempts: I've tried "Opportunities w/ Payments and GAUs", but consistently run into an issue (regardless of whether I'm using cross filters/ whether I include a "does not equal "" " filter where GAUs populate as blank, despite very much existing). Based on very generous suggestions from an earlier thread, I tried to begin with "GAU Opportunities with Payment" (and "GAU Opportunities with Opportunity"), but in both cases could not add the fields I needed for the other (close date and payment date, respectively). It seems that the issue is due to the whole with/ without thing, and so I tried to make a custom report, but cannot seem to create a report type that allows me a sufficient degree of flexibility.
@Ryan McCracken those blank GAU rows are the join, not bad data. A payment and a GAU allocation are both children of the opportunity. A custom report type can walk down one of those, not both. That is why one type has close date and the GAU, and the other has payment date, and the combined type shows a blank GAU.
Campaign is on the opportunity, so that half is easy. Opportunities with Payments, filter Campaign, Close Date, and Payment Date.
For a GAU, use Opportunities with GAU Allocations and filter the GAU plus Close Date. Payment Date will not be on that report. A joined report can sit the two side by side on Opportunity Id, and the amounts will repeat when one opportunity has several payments and several allocations.
If you need one row that is a payment, a GAU, and a payment date, that is what Payment Allocations are for. Without them, NPSP never stored which payment funded which GAU.
