Opportunities should be records
Make Opportunities/Proposals a record type, like Constituents, Gifts, Actions, etc. We need it to be easier to export specific opportunities/proposals for constituents in our exported lists. We cannot refine the output on Opportunities the same way we can with gifts and actions. This is a huge problem. It is difficult to bulk update opportunities/proposals in database view because of it.
This is a problem that has existed in database view. If unified view is designed for streamline fundraising and be fore fundraisers, making it easier to report on and bulk update specific opportunities should be a priority and updated in unifed view.
-
Christina Williams
- May 14 2026
- Reviewed: Voting Open
Related ideas
Part of this needs to be making Proposal/Opportunity system record ID available in query. I need to be able to pull a list of all Proposals/Opportunities with only 1 fundraiser listed when my output includes that field in order to calculate metrics for each fundraiser. When I pull it out of query, it's missing system record ID to identify the unique count of the proposals/opportunities, but when I pull it from Lists, I'm stuck with multiple fundraisers listed in the same column.
yes- this would solve several problems we have with opportunity lists!
Yes I would love this! I am troubleshooting how to pull a report or opportunity list, anything! for my grants team and it would make it much easier if queries could be by opportunity instead of constituent. Or if opportunity lists had many more fields!