Share
ReportWe are currently building a new Customer Experience platform for a non-profit organisation, utilising the Fundraising and Engagement module among other areas. We need to be able to group our individuals into families, and are using the Household Account type for this. We can receive donations, or may solicit for donations, from families (i.e. Households) as well as from companies or individuals.
I can add an Account record with an Account Type of Household to a Transaction record using the customerid field, so recording the income appears to pose no problem. However, if I try and add a Household type Account record to an Opportunity which is where we record Solicitations, the system rejects it.
Our integration partner has suggested using the direct Account relationship (parentaccountid) rather than the customerid field for Households, but that would mean the data structure for a solicitation from a Household would then be inconsistent with all other solicitations, so this is not a good solution.
The customerid field on Opportunity appears to be configured in exactly the same way as the one of the same name in Transaction entity, so I can't seem to find any config that is causing this issue and wondering if it is a bug?
Thanks,
Jen
I have the same question (0)
All responses (
Answers (
150
