A: When PowerView collects the data from the different sub views only one match on an object can be handled. If there are two views that return the same object (for example two views contain a match on the same Incident) then PowerView would have to pick one of these. Since these two object can contain different amount of data (depending on which combination class that was used) there is a possibility that PowerView would pick one of the object the user did not expect and display too little data.
To warn the user that the scenario above is about to happen, there is a constraint that if two sub views target the same class (example: Incident) but do not share the same combination class, PowerView will display a warning.
Please sign in to leave a comment.