-
Add smart query filters that are not included in the original ad-hoc query
We need to create a smart query in which users can filter by a number of recognition credit fields, including a SUM value for the total amount of recognitions received by each constituent. We need to see one row of results for each constituent - n...0
-
Ability to Query on Tributes in Constituent Records
When creating an ad-hoc Constituent Query you cannot access the tribute fields – the tribute node is not available (only tribute revenue and tribute acknowledgement correspondence). This is required for reporting on tribute activity and has been r...0
-
Unable to query off of Admin, sites to ensure that we filled it out properly
User would like to query off of all sites under administration.0
-
Reflect all available options for “GL Post Status” in Ad-hoc Query criteria
Currently, Ad-Hoc Query has these options for the criteria of GL Post Status: "posted", "not posted", and "do not post". But on the transaction page, the Post Status could also be "posted - activity pending status" Because of this mismatch, transa...1 Reviewed: Voting Open
-
Add ability to query on recognition credits for membership installment plans
Currently, the Revenue Recognition Credit Query view cannot pull in non revenue data (i.e. an unpaid membership Installment plan). The Recognition types are entirely related to revenue. However, it would be useful to have the ability to query on r...0 Reviewed: Voting Open
-
Add an additional node on the Constituent Source view that allows users the ability to query on a specific Prospect Plan interaction that will also included that interactions Prospect Plan name.
When creating a query using the Constituent Source view, users would like the ability to query on a specific Prospect Plan interaction that will also included that interactions Prospect Plan name.0 Reviewed: Voting Open
-
When using a query, be able to query on and exlude households where both members are deceased.
Currently CRM does not have the functionality to query on households were both members are deceased, you can also not exclude household records where both members are deceased.0
-
Add "Not" functionality to Query Builder
Very helpful logic when building queries, and would avoid having to set up additional selections to perform the same function (which both slow queries down and take up additional space in the DB)0 Reviewed: Voting Open
-
Add an 'export to XML file' feature in query
Add an 'export to XML file' feature in query, similar to export csv. -
Active User Query to show is User is being Run as another User or Login as themselves
When using the active user query, it would be helpful to show if the user is logged in as themselves, or if they are being run as another user.0 Reviewed: Voting Open