-
The Overdue Asks for an opportunity should be based on the expected ask date.
Currently Overdue Asks for a prospect are based on the opportunity ask date. From a workflow standpoint it would make more sense to have Overdue Asks based on the expected ask date.0
-
Add constituent field to the research request form
Add a constituent field to the research request form so that researchers managing the unassigned requests can fully understand the request.0
-
Enhance File a contact report form for next step in a prospect plan when no step is defined. Include fields and functionality similar to Edit next step information.
Enhance File a contact report form for next step in a prospect plan when no step is defined. Include fields and functionality similar to Edit next step information. Fundraisers prefer to complete next step information at the time of filing a conta... -
Telephone numbers not visible on Planned Records view
It will be helpful when reviewing Planned records that we able to view constituents contact information. (ex. phone number)0
-
allow fields to be updatable in a datalist
There are many fields we display in datalists that would be great to be able to update in the list instead of having to 'Go to Constituent' or 'Go to Plan'. An example is opportunity dates/amounts on the My Fundraiser Page or on custom datalists.0
-
Add the Mapping Feature component for Canadian customers
The Mapping feature component of the ResearchPoint module isn't available to Canadian customers0
-
allow us to add columns to research groups
It would be nice to be able to add columns to research groups.0
-
Recalculate Household capacity ratings for all records
Currently, there is an option to apply a wealth calculation to all records. However, that does not apply the calculation to households - only to individuals.0
-
Consistent Validate and Commit logic in Sponsorship Batch
Because the Validate process only validates against the BBCRM database, and not other rows in the same batch, some checks may be successful during Validate but produce exceptions during Commit. For example, -"No Matching Opportunity" -“Duplicate...
0
Will not implement
-
Add a unique Planned Gift Number to a Planned Gift Record
It would be great if a unique identifier was added to a new planned gift record. Similar to a lookup ID, revenue ID, or interaction ID. The same outcome for opportunity records would be great.0