# How to apply aggregations and filters on aggregated data **URL:** \ **Category:** Kibana\ **Created:** [March 6, 2019, 3:40pm UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144 "2019-03-06T15:40:06Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![adityaPsl](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@adityaPsl](https://discuss.elastic.co/u/adityaPsl)\ **Post date:** [March 6, 2019, 3:40pm UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144/1 "2019-03-06T15:40:06Z")
Hello Team, I have a use case where i need to apply filters and metrics on aggregated data. for example i have below employee promotion data. ``` +----+-------+------+-------------+---------------------+ | id | empid | name | designation | promdate | +----+-------+------+-------------+---------------------+ | 1 | e1 | aa | d1 | 2019-03-06 20:28:45 | | 2 | e2 | bb | d2 | 2019-03-06 20:29:18 | | 3 | e1 | aa | d2 | 2019-03-06 20:29:28 | | 4 | e2 | bb | d3 | 2019-03-06 20:29:41 | | 5 | e3 | cc | d4 | 2019-03-06 20:30:22 | | 6 | e3 | cc | d5 | 2019-03-06 20:30:36 | +----+-------+------+-------------+---------------------+ ``` aggregated data based on empid ``` +----+-------+------+-------------+---------------------+ | id | empid | name | designation | promdate | +----+-------+------+-------------+---------------------+ | 6 | e3 | cc | d5 | 2019-03-06 20:30:36 | | 4 | e2 | bb | d3 | 2019-03-06 20:29:41 | | 3 | e1 | aa | d2 | 2019-03-06 20:29:28 | +----+-------+------+-------------+---------------------+ ``` and i want to apply count and filter as employees in designation d5 should not be part of the list and count the employees not having designation as d5. using Kibana data table visualization i was able to get the latest unique value of employee but not able to apply filters and count aggregations on the data which is aggregated by empid. any pointers to resolve this issue is really appreciated. Thank you for your help and support. Thank you, Aditya ---
**Author:** ![ppisljar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppisljar/32/11588_2.png) [@ppisljar](https://discuss.elastic.co/u/ppisljar)\ **Post date:** [March 7, 2019, 1:59pm UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144/2 "2019-03-07T13:59:23Z")
could you also show how your expected output would look like ? if you want to filter our all employes with designation d5 from data just add a filter to the filter bar: - click the add filter button in the filter bar - select field designation - select 'not one of' - enter 'd5' if you save your visualizations the filters you added will be saved with it. ---
**Author:** ![adityaPsl](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@adityaPsl](https://discuss.elastic.co/u/adityaPsl)\ **Post date:** [March 7, 2019, 2:57pm UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144/3 "2019-03-07T14:57:39Z")
Thank you ppisljar for your reply. ``` the final output should look like this ----+-------+------+-------------+---------------------+-------+------+------ id | empid | name | designation | promdate 4 | e2 | bb | d3 | 2019-03-06 20:29:41 3 | e1 | aa | d2 | 2019-03-06 20:29:28 ``` ----+-------+------+-------------+---------------------+-------+---- basically it should show the latest promotion received by the employee but not d5. I tried the solution you mentioned , but when i try to apply filter it gets applied to the aggregated result and employee 'e3' is shown with its 'd4'promotion but that is not intended. as a workaround i am creating a one more index with empid as primary key , so there will be only one and latest record available in the new index and applying aggregations like count and filters on that data. However i am not sure if this is the right and recommended way to handle the situation. any thoughts or suggestions are really appreciated. Thank you very much for your help and support. Thank you, Aditya ---
**Author:** ![adityaPsl](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@adityaPsl](https://discuss.elastic.co/u/adityaPsl)\ **Post date:** [March 12, 2019, 12:05pm UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144/4 "2019-03-12T12:05:18Z")
Hello Team, Just wanted to check if there is an option to get unique latest record for employee and create saved search and create data table or aggregation on that saved search. Thank you for your help and support. Thank you, Aditya ---
**Author:** ![adityaPsl](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@adityaPsl](https://discuss.elastic.co/u/adityaPsl)\ **Post date:** [March 17, 2019, 11:12am UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144/5 "2019-03-17T11:12:09Z")
Hello Team, Could you please help me with pointers for applying metrics like count , sum or filters on aggregated data based on unique field. for above use case a query similar to ``` select emp.empid,emp.name,emp.promdate,emp.designation from emp inner join (select empid,name,designation,max(promdate) as latest from emp group by empid) r on emp.promdate = r.latest and emp.e mpid = r.empid where emp.designation !='d5' order by promdate desc; ``` and output would be latest promotion details with d5 excluded ``` +-------+------+---------------------+-------------+ | empid | name | promdate | designation | +-------+------+---------------------+-------------+ | e2 | bb | 2019-03-06 20:29:41 | d3 | | e1 | aa | 2019-03-06 20:29:28 | d2 | +-------+------+---------------------+-------------+ ``` any pointers to resolve the issue are really appreciated. Thank you, Aditya ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 14, 2019, 11:12am UTC](https://discuss.elastic.co/t/how-to-apply-aggregations-and-filters-on-aggregated-data/171144/6 "2019-04-14T11:12:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.