Paginated Report Parameter issues/broken/not working - Potential BUG! - Cascading Parameters

[ajohnso2]

Hi All,

I've reached the end of my tether and reaching out for help at this point - I have used paginated reports previously for years in its former guise of SSRS so I am aware that what I am trying to achieve is possible (And works exactly as expected in Desktop & Report Builder) - Issues come once the report is deployed to the service, which is where I think I have found a bug.

1 parameter value is passed in from PBI desktop "Cost Centre Source" - everything is then derived from 2 datasets based on the value.

Microsoft I hope you read this!!

From Report Builder cascading prompts working exactly as expected:

From PBI desktop embedded Paginated Report Visual - Also everything working exactly as expected...

From report published to the service everything works as expected on the initial report rendering, once a new cost centre is selected none of the child parameters are updated. 

I would really appreciate any help.

[ajohnso2]

Please see my original post detailing the issue

https://community.fabric.microsoft.com/t5/Service/Paginated-Report-Parameter-issues-broken-not-worki... 

[Anonymous]

Hi @ajohnso2 ,

Could you please provide the desensitized example data? 

It is very helpful for me to test in my environment.

Thanks for your efforts & time in advance.

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ajohnso2]

*bump

Ill be moving this thread back to issues if no response 

[bradsy]

Hi ajohnso2,

Did you figure this out? We recently fixed a bug in the paginated visual where parameters where not posting back correctly. The fix is in safe rollout process and should be in Prod ~3 weeks. As a workaround until it rolls out, this was suggested 1) change the parameters in the RDL to allow multiple values or 2) they can change the parameter mappings on the visual to use an aggregation (such as "First") that will send a single value to the RDL report. 

Hope that helps!

[ajohnso2]

Can you confirm if this fix was implemented? I do not see any notes about it on the August update and the issue still remains.

[bradsy]

Hi ajohnso2, 

Sorry to hear it is not fixed yet. From what I can see the final change made a release train with current ETA ~Sept 13. If the fix does not work, please feel free to file a support request so that we can get your repro and get it properly fixed.

[ajohnso2]

Hi,

This issue is now marked as Resolved in the latest Oct release and added to the 'Fixed Issues' section of the forums - Issue ID: 825

I just want to bring to your attention that this is not resolved and the issue can still be seen from the sample pbix and rdl attached in this thread.

[ajohnso2]

Thanks for the response bradsy, I have implemented a work around for now whereby the paginated report is opened via a URL for now - this means the user is forced to submit the report request with the parameter values embedded in the URL.

I will keep my eyes peeled for your fix roll out - many thanks.

Andy

[ajohnso2]

*Bump

[ajohnso2]

Hi, is there any update to this issue?

[bradsy]

Hi ajohnso2,

Can you file a support request? This will get people dedicated to investigate the issue.

[ajohnso2]

Thankyou for your reply - I have attached a very simple .rdl and pbix file. You will see the issue only applies once the reports are deployed to the service and viewed. In PBI desktop and Report Builder the parameter behaviour is exactly as expected with default values automatically updating.

PBITestPaginatedReportParams.pbix

TestParams.rdl

Look forward to your response.

Andy