# Still experiencing Dashboard issue after 3.2 upgrade

**URL:** https://community.graylog.org/t/still-experiencing-dashboard-issue-after-3-2-upgrade/16069
**Category:** Graylog Central (peer support)
**Created:** [June 24, 2020, 9:47pm UTC](https://community.graylog.org/t/still-experiencing-dashboard-issue-after-3-2-upgrade/16069 "2020-06-24T21:47:07Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![jamiebuxxx](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jamiebuxxx/32/1646_2.png) [@jamiebuxxx](https://community.graylog.org/u/jamiebuxxx)
#### Post date: [June 24, 2020, 9:47pm UTC](https://community.graylog.org/t/still-experiencing-dashboard-issue-after-3-2-upgrade/16069/1 "2020-06-24T21:47:07Z")

</div>

Hello,

I wanted to bring this issue back up to see if there are more details on the solution.  
[https://community.graylog.org/t/solution-to-dashboard-issue-after-3-2-upgrade](https://community.graylog.org/t/solution-to-dashboard-issue-after-3-2-upgrade)

I have tried using Robo3T(in text mode) and even had our DBAs to take a look, but we were not able to find any `null` time row config in the `views` collection. The DBAs were curious if there is a MongoDB query that can used to find the affected value? When trying to use the following query, we do not get any results.

```auto
where quantity is a positive number and unit [smhdwM]

```

We really would like to upgrade, but unfortunately this is a blocker as we can not simply drop our collection and start over.

Thanks!

---

_[View the full topic](https://community.graylog.org/t/still-experiencing-dashboard-issue-after-3-2-upgrade/16069)._