compound queries could add or subtract more than one query at a time
I have a suggestion regarding new compound queries, and to explain it, I will give you one example of many that I deal with regularly.
Recently I created a mailing list built upon a set of queries where I first had to single out ten different groups of accounts. I numbered each of the queries, 1 through 10.
Then I needed to add all ten queries together, so
query 11 = 1+2,
query 12 = 3+4,
query 13 = 5+6,
query 14 = 7+8,
query 15 = 9+10,
query 16 = query 11 (1+2) + query 12 (3+4),
query 17 = query 13 (5+6) + query 14 (7+8),
query 18 = query 15 (9+10) + query 16 (1+2+3+4),
query 19 = query 18 (1+2+3+4+9+10) + query 17 (5+6+7+8) = full list.
Now (Query 20) I can subtract accounts with various "do not mail" fields, creating my final list.
My suggestion is, on new compound queries, give users the capability of choosing exactly how many queries to Add together at one time (sort of like how many files to upload when updating a website).
In my example, I would still need to create queries 1 through 10, but if I could choose, in a single compound query, to start with query 1 and add 9 more, it could have saved me hours of work on this project alone (which is slowed down even more because I am constantly interrupted with phone calls, people popping in, and sporadic work on dozens of projects that I am have going).
It would have reduced the number of queries steps from 20 to 12.
Subtract might be another candidate for subtracting multiple queries from an initial query.
Intersect I have used only very occasionally, so I don't have much to say about multiple Intersects. I don't know how useful they would be, but if you're doing it for Add and Subtract, I suppose you might as well consider multiple Intersects so "all of the children are treated the same".
-
Guest
- Aug 7 2015
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +413
Related ideas
Kimberly - thank you for the detailed update. It would be great to have more similar updates on other popular ideas even if it is an explanation as to why the idea is not feasible
One trick I do to get around these situations is to create a UDF in the account. I created a Data category, then an Import Flag sub category. I create a new value and use a simple code. The downside is that if it's a large file it'll take many imports as they only allow for 2,000 records at a time. Once all are coded, just run a query on that one code to use for your report.
Product Update: We've researched this and figured out a way to add the functionality to eTap. First we're going to make an update to our query picker functionality that will allow for a better UI experience when we do implement the ability to add or subtract more than one query at a time. We plan to release the new query picker in 2023. As far as the compound query update, I don't have an ETA for that yet. I would LOVE to get it in still this year, but realistically we may not be able to get to it until 2024. I will try to keep this idea updated with a more specific timeline once I have one.
YES...YES...YES!!!!! This would save SO MUCH time and frustration!!! This was suggested all the way back in 2015!!!! It's been over SEVEN YEARS!!! Why has this not been implemented?????
Yes! This is a feature with Bloomerang our organization is looking in to. It would help make eTap a more comparable program.
Good gracious, yes!! So cumbersome as it is.
Wonderful idea. The compound query process is very frustrating.
Absolutely. Very time consuming process with only one at a time.
Agree. SRO allows this... AND this, ANT NOT this... etc.
Like the old school If, then statements :-)
This would be great. I find myself creating compound query on top of compound query to get to the info that I need.