In Database view, you can select a query from the list of queries (highlight it) and down below you see everywhere in the system that the query is being used. This is incredibly valuable information - especially for query clean-up. I remember throwing a party when that update hit database view.
Unfortunately, this functionality did not make it over to webview. Please include functionality so we can easily see if a query is in use anywhere in RE to webview query. Without it, someone may accidently delete a query that was used for a process, and it will be nearly impossible to identify where a query is being used without opening every single existing export, report, etc.
Knowing where queries are used (not just when last run) in web view would help keep the number manageable.
This is so very important. I can't ten you how many times I've gone until the query and used this feature to figure out what export or report or merged query I need to track down to run a process when I can't remember the exact name at my next step. And it's also helpful to know if I should make a copy of the query instead of changing the query criteria.
For the sake of database management, this is a needed functionality or we will end up with tens of thousands of queries because we cannot identify their uses to determine what can be purged.
Definitely need to see this information so we can clean up old queries.
I agree - this is a significant loss!
This is an incredibly helpful tool for historical checks and cleanup. Without the ability to check if a query is being used somewhere, there is the unfortunate risk of a query that is used on a lesser basis that is integral to a process being deleted. Some of these types of queries can be quite complex, and re-creating them a burden.
This was SUCH a good add when it came to database view. Please include this so we don't go backward. Again.
Yes, please! The ability to see if a query is used in/linked to a merged query, business rule, queue, saved report, export, global change, or mailing help prevent us from breaking any established processes. If web view also had this, then along with the new functionality of being able to see a report's last used date it would be a huge improvement helping data managers clean up saved queries.
Yes! Having the ability to see WHERE else the query is used gives a better picture of that query. Not all queries are stand-alone objects. If I can see that I have used a certain query in Exports, Reports, ect., With this knowledge, I can determine if I need to build a new query or if it is safe to modify the existing query without unintended consequences.