Building analytical systems are no different than building any other software; under certain situations, things may go wrong. Sometimes, those situations are even expected and you know up front they may occur under certain conditions.
In other cases, things may go wrong "by design", depending on the solution you're designing.
For example, one may configure a certain visual metric set to deny access from a certain group of users. If those users are now loading a dashboard that contains that metric set, they will get an error message indicating their access is denied.
In other cases, the error may not be expected at first but changes in other areas (data structure or else) may trigger them. For developers and content creators, the error messages are often beneficial, helping them to create a better solution. However, for content consumers, these error messages may be annoying or meaningless.
Dundas BI allows you to handle the errors in different ways so you can provide an optimal experience for your consumers. For example, if you are building a solution for your external customers or high-level execs and you want to make sure they never see an error message, you can configure the application to Ignore Inline Errors.
This is done under the admin -> setup -> config screen as detailed HERE and showcased in the image below. In addition, each visualization offers a Data Error action where you can configure your own action (i.e., change layer to show a layer with your own custom message instead) or even provide a script to handle the situation using your own custom logic.
Using these configurations – you can provide an even smoother experience to your consumers, avoiding unnecessary frustrations.
