Blank output from a session whose filters are right is a data availability problem. The scenario is addressed by the following: the session ' s data extraction to Caboodle. SlicerDicer can only summarize what is in the warehouse, so the first thing to verify is that the required data has been extracted and loaded. Other settings, including security and report groups, influence visibility and do not explain an empty result for a user who can open the session. The developer should confirm the extract schedule, review the logs for errors and check that the relevant fact table contains rows for the selected period. When the data is found to be missing, the mapping or the schedule should be corrected and the load rerun. Testing the session again with a broad population, then narrowing it step by step, is an efficient way to locate any criterion that eliminates the remaining rows. Where several settings could plausibly be responsible, changing one at a time and retesting after each change makes it possible to learn which setting actually solved the problem, which is useful knowledge for later maintenance.
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