Hi richgalloway, All the group names are the same, the cs_uri_stem values are mostly the same as the group value, with the exception of 2 rows which showed a different value. I can provide the results if that would be helpful. I appreciate your assistance; I want to take another look at what I have done recently independent to your suggestions and make sure what you are thinking is going to get my user what he wants in the end. I want to make sure I am being clear in my explanation. I have run 2 test searches. In the first one, I manually set the value of cs_uri_stem to a value in the lookup, for example, /uri_1* and I count by cs_uri_stem. This gives me 3 rows (for this example) "/uri_1" "/uri_1/subA" "/uri_1/subB" Each row in the result gives me the parameter values specific to that row. The rows when taken together equal a "group" for the lookup entry /url_1* In the second search I again manually set cs_uri_stem= /uri_1* but this time I do not count by cs_uri_stem. I just count the number of events returned. This returns one row which contains the data for the 3 rows returned in the sample search above., which gives me the combined data values for the "group" /uri_1*. What my user wants is a report with each row listing the Group name( in this case /uri_1*) but with the combined data for /uri_1 plus any sub uri returned. So, intuitively, it seems that what is needed is to run the search with the first group name only counting the total events, then save the results of that search before executing the next search with the second group in the lookup, etc; somehow ending up with a report where each row shows the group name and the combined data for that group. Maybe there is totally different way to do it? Please let me know if you have any question about how I am explaining the issue. Appreciate your help peter
... View more