Welcome to Luminate Ideas!
Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
Allow customized date ranges in queries
A customer suggested that it would be very useful to be able to specify a date range when selecting your query logic. This is because he would like to be able to run a transaction query from 2012 and compare it with 2013. The closest options for him to do this would be to use previous year, but that wouldn't let him pull data from the year before. This feature would also be useful to support so we can provide workarounds in case there is something wrong with other query logics such as previous year or YTD. �
-
Ken Cantu
- Mar 31 2015
- Reviewed: Voting Open
Related ideas
Privacy Policy | Safe Harbor Notice | Terms of Use | Acceptable Use Policy | © 2019 Blackbaud, Inc. All Rights Reserved
I understand now. So you want to, for example, email anyone who gave $50 or more within a specific date range? If so, sounds good, I am actually working on next gen of querying and segmentation now so I will add this requirement in. Thanks!
Ken
We are trying to identify who in our database has made a gift or opened an email each month (without duplicates). The query is built, we just don't have the ability to restrict the interactions to a specific date range.
This sounds like something best achieved through our reporting tool and not the query tool. In reporting you have the ability to pull transactions and specify date ranges. If that won't work for you can you walk me through how you are using query tool's information after you pull the data?
Thanks for submitting your idea,
Ken