Dashboard POI limitations that is very annoying
Answered
I've had extensive contact with you guys about a super super simple issue on your Dashboard. Namely that the so called Account Level POIs (the one that are visible on every route) are not all loaded on the dashboard.
During my holiday a few months ago I have raised the issue. First they tell me there is no kind of limit and that they can't reproduce it. Then after I did hours of testing I found out it was a simple flaw in your code. When fetching POIs you only fetch the last 100. So all POIs older are no shown. I actually rewrote the Javascript manually in a few mintues to fix it. It's really really simple to fix. For me this is an annoying issue because I can't even see my home POI anymore on the Dashboard.
So when is this finally fixed? Last time I asked about it I got a vague answer about it. Make up your minds and for the time being just show me my POIs so I can see them all and decrease the amount if needed...
-
Hi Gerben, the functionality was available for unlimited usage and it was restricted with limitations only a few months back. We have reported it with the team, and it is low priority because of it not been a typical use case so far, and requires a bigger change. Any request only gets actioned by the impact and the number of user affected by it.
-
So you're saying you guys don't care because I'm the first to raise the issue - gotcha. As you can see more people are starting to follow this, and a few people on Facebook told me they had the same.
The most annoying part is that I have created more than 100 POIs which was no issue at all. There was no notification or message or whatsoever, you also told me there's no limitation whatsoever.
And now you tell me that you're not fixing this bug, and suck it.
Even no single time you expressed your appreciation of finding (and providing a fix!) a bug, because that's what this is.
So you're saying my important POIs like my Home location will no longer be visible on my Dashboard because I used a feature without limitations that's improperly fetched? Thanks again for the lack of help. I guess I'll just have to switch back to Komoot again and sync my routes there. You guys clearly are not interested in improving your product.
-
Hey Gerban. We apologies for the inconvenience caused to you. We do actually appreciate you for bringing this up to us. We have taken this to our team to see what best we can do for this. You would have seen the delay in the response to this post. The reason for this was our investigation and isolation for this issue to ensure we start in the correct way.
It certainly true that we improvise our product with the feedback and suggestion we get from you folks. However, we have to see how beneficial it would be for our users and if it stands on the majority, we certainly will have this implemented. But this issue is something we have to look into and for this, we have sought our developers' help.
-
@Gerben Bol. How to get the Account Level POIs (the one that are visible on every route) visible on the screen?
Can I f.e. mark a spot where I can take a ferry from? Or two marks on both side of the Canal?
And will that same information, these two created spots, displayed in my next 'newly' created route?
-
Hi Vincent, yes you can do that as a Route level (or account level if you wish). Account-level will appear on all your routes, where as Route level will appear only on that particular route.
Check out the details here: https://support.hammerhead.io/hc/en-us/articles/360040807874
Please sign in to leave a comment.
Comments
8 comments