Disable Query Expressions
When the world is your oyster, there are many ways you can go about solving issues. With Axonius, the primary issue the users run into is figuring out what data you may want and what combination works just right for the query. With the Disable Query Expression, we can help get you just a little closer to making query checking an easier reality!
What is it used for?
The query expression is a feature released in the 4.6 module that is designed to help you quickly check data with the expression vs without. Many customers will want to validate data sets OR be at a place where they have to build out many different versions of the same query. By being able to disable the query expression in the query wizard, you can pivot quickly between these tasks.
The Disable Query Expression button can be found in the query wizard on the right side between the filter and cancel icons (see image below).
Think of utilizing this function in the same way we utilize the query intersection function. With the query intersection, there is a base query and intersecting query.
Here is a simple illustration to explain the parallel. Below you will see a standard Query intersection where the base query is "All Windows Devices" and the intersection is "Devices seen in the last 0-30 days." The intersecting number comes out to 154 of 603 items.
We can get the same information in the query wizard by utilizing the Disable Query Expression tool. On the first image below, you will see that we brought in the base query of All windows devices. Our number is 603 as is in the query.
Now we are going to test to see what the intersection is. We come up with 154 devices.
We can go about adding and taking away but with the disable query expressions feature, we can have both of the items in and we can look at the base number and enable the query expression and then look at the intersection.
While it is not a visual output that is as nice to look at as the query intersection, It definitely gets the job done with more ease.
The other great thing is that you can look at many different intersections vs the standard 2 that are available with the query intersection chart.
Points to Ponder
Just like the query expression, you want to make sure you are aware of your query logic when you are looking at everything. If you happen to have a query that has many OR functions and you disable an expression, you may find that you don’t get what you think you should get.
If the number doesn’t turn out what you think it should, check your logic structure.
**Always remember that when you are dealing with a negative expression you generally will want to use the AND NOT function vs the OR not function.**
End of the day, think of everything we do as a venn diagram where you are collecting data. This feature simply helps you toggle between the layers of the venn diagram vs having to delete and re-enter items.
Please sign in to leave a comment.