# Aggregation by Maximum Date Doesn't Work Well
**URL:** https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752
**Category:** Kibana
**Created:** [July 29, 2019, 5:21pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752 "2019-07-29T17:21:36Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Carlos.limaElaw](https://discuss.elastic.co/u/Carlos.limaElaw)
#### Post date: [July 29, 2019, 5:21pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752/1 "2019-07-29T17:21:36Z")
Hi, there!
I'm trying to sort a vertical bar Chart by a agregation of maximum date like this:
**"cc\_mes\_ano\_registro"** is a scripted field that returns the Month
and Year of a date field( **data\_de\_registro** ) as a string (because string fields are aligned in the center of bars as you can see in "December - 2018"), but there's a problem:
As you can see, March, July and August - 2018 are ahead of July 2019.
In other words, it is not ordered by the maximum date in each bucket.
And if I order by descending it goes like this:
It's completely different.
This is the "cc\_mes\_ano\_registro" script:
```
if(doc['data_de_registro'].size() > 0 ){
def registroMillis = doc['data_de_registro'].value.getMillis();
ZoneId timeZone = ZoneId.of(ZoneId.SHORT_IDS.get('BET'));
LocalDate dataRegistro =
LocalDateTime.ofInstant(Instant.ofEpochMilli(registroMillis),timeZone).toLocalDate();
def mesAno = dataRegistro.getMonth()+" - "+dataRegistro.getYear();
return mesAno;
}
return "N/A";
```
Some solution, something wrong that I can't see or it's just a bug?
Thank you!
---
### Author:  [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)
#### Post date: [July 29, 2019, 10:56pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752/2 "2019-07-29T22:56:15Z")
Is there a reason you are not using a Date Histogram aggregation? It might make this much easier without the need for a scripted field.
---
### Author:  [@Carlos.limaElaw](https://discuss.elastic.co/u/Carlos.limaElaw)
#### Post date: [July 31, 2019, 2:28pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752/3 "2019-07-31T14:28:12Z")
Hi, Nick! Thanks for response me.
I'm using a scripted field because Date Histogram put the label in the bar's corner and I need in the middle.
---
### Author:  [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)
#### Post date: [July 31, 2019, 6:03pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752/4 "2019-07-31T18:03:17Z")
HI Carlos,
I see now. We have an enhancement request for this already. [https://github.com/elastic/kibana/issues/38494](https://github.com/elastic/kibana/issues/38494)
You can use the Inspect button on your Visualization to see the results of the query. You can also change the View from Data to Requests to see the request and response sent to/from Elasticsearch. This might offer a clue why the ordering is not what you are looking for. [https://www.elastic.co/guide/en/kibana/current/vis-inspector.html](https://www.elastic.co/guide/en/kibana/current/vis-inspector.html)
---
### Author:  [@Carlos.limaElaw](https://discuss.elastic.co/u/Carlos.limaElaw)
#### Post date: [July 31, 2019, 7:55pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752/5 "2019-07-31T19:55:12Z")
I discovered something!
My field local\_trabalho.keyword have some null data, and this is breaking the axis order.
So I did a scripted field that returns "N/I" for null values and solved the problem.
Thanks for answer me anyway!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 28, 2019, 7:55pm UTC](https://discuss.elastic.co/t/aggregation-by-maximum-date-doesnt-work-well/192752/6 "2019-08-28T19:55:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.