Blank Paginated Report Visual Generated

[shrikantkale32]

We have a use case where we are embedding paginated report inside a powerbi report using the paginated report visual. We have 4-5 drop down slicers that affect the paginated visual. These slicers use the same powerbi field that is connected to paginated report parameters. We noticed that for certain slicer selections, no value is passed to paginated report parameters and thus the report is not generated. Is there a way to ensure that some values are always passed for each parameter in paginated report even if the combination of slicers selected by user does not have any data?

[shrikantkale32]

Thanks for your reply @nandic . The parameter selection in paginated report works fine for any combination of selection (for some cases empty report with only table column headers and static text is created which is fine). Just a note, we have turned off cascading parameters in paginated report and slicer interactions between drop-downs in PBI report. This is done to improve performance for individual drop-down slicers. 

I believe the issue arises when user selects a combination of slicers for which there is no data within the datasource table and thus the value passed for paginated report parameter is empty. I want to understand is there a way to always send a defualt value in such a scenario. Also, we want to pass the values from PBI report to paginated report instead of assigning a default value within paginated report so that paginated report always reloads. Our current observation is that when no values are passed from PBI to paginated report, the paginated report visual does not reload.

[nandic]

@shrikantkale32 here is basic demo to check if everything is setup correctly: https://www.youtube.com/watch?v=5Fcf8eXRq2E 

But based on your text, both paginated report and power bi report use same model, same fields with same name so the mapping should be correct.

Then we go to next issue, you mentioned that "certain" slicer selection doesn't work. Does same parameters selection work fine on paginated report?
Is there anything specific with these "problematic" parameters/slicers? (specific type, specific available values etc or it is related to selected item within slicer)?

Cheers,
Nemanja Andic