We keep hitting an issue where something minor gets changed in our database (in an ideal world this wouldn’t happen, but it does).
The problem I have is that QS seems completely incapable of handing this gracefully.
This Visual itself shows this:
Which is understandable, but then when you look at the field list you just see this:
Has anybody figured out a workaround for this? We’re currently having to create shadow documents with the mapping for every bit of analysis to fall back on when QS isn’t able to handle the change.
In an ideal world (and this is the the feature request bit), I would want QS to keep a cached name of what this field was, even if it doesn’t exist now. I.e. it would say
– Missing field – was “Last login date”
It seems an extremely flimsy part of the system. We’ve had to spend a lot of time and effort recovering from this (and now spend more time writing backup notes then actually designing dashboards), when if QS kept some sort of backup record of the field it would take seconds to recover.