When an analyst needs to understand or reuse the logic behind a SlicerDicer session, the Get SQL option on the session toolbar provides the query that the session runs. This is useful for validating results, for troubleshooting differences between SlicerDicer and a custom report, and for giving a developer a starting point for a more complex query. The second option is correct. Clicking Export Results produces the data from the session but not the query that generated it. Enabling proxy and debug is not the method, and Proxy Mode does not reveal queries. Submitting a TID request would involve Epic support for a matter that the tool already supports directly. Having access to the SQL does not alter the self-service nature of the tool. The query reflects the data model, base, criteria, slices and measure that the user selected, so it provides a transparent view of how the population was defined. Analysts should keep in mind that the query reads from the warehouse and that its availability may depend on the user ' s security.
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