A recognized limitation of SlicerDicer is that it cannot perform multi-table joins or analysis outside the data available in Caboodle data models. The user works within a model that has been designed for a subject, and the tool does not allow arbitrary combination of tables or the introduction of external data. Requirements of that nature are met with SQL against Clarity or Caboodle, by a developer who can control the joins and logic. The other options describe normal behavior or strengths. Exporting to Excel is an available function that allows results to be used elsewhere, so it is a feature and not a limitation. Displaying data from the live Hyperspace instance is not accurate, as SlicerDicer reads from the warehouse, but that statement would not describe a limitation of the kind the question asks for. Supporting grouping by provider and specialty is a strength, since it is achieved by adding slices. When a stakeholder requests an analysis that would require combining data in ways the model does not allow, the analyst should explain the constraint and propose an alternative, such as a custom report or an extension of the model by a Caboodle developer.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit