Forum Discussion
Paginated Reports - Dynamic subscription
Has anyone tried to use this feature yet? More about this annoucement here
We've been waiting for this one but, I am getting this error when I try to setup the dynamic subscription. I have email field in the dataset etc., not sure what I'm missing.
web.subscription-pane-lazy.min.3d065f6148a102b93e2f.js:1 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://paginated-reports.powerbi.com') does not match the recipient window's origin ('https://app.powerbi.com').
TIA
-Pawan
3 Replies
- AnonymousNot applicable
Hi pvuppala ,
Dynamic email subscriptions are only available for paginated reports in the Power BI service, not for other types of reports or dashboards. You need to have a Power BI Premium or Premium Per User license to use this feature.
One possible cause is that the email field in the dataset is not formatted as text, but as a different data type. You can check and change the data type of the email field in Power Query Editor.
Another possible cause is that the email field in the dataset contains invalid or blank values, which prevent the subscription from being created. You can use filters or transformations in Power Query Editor to remove or replace any invalid or blank values in the email field.FAQs about Troubleshoot subscribing to dashboards and reports - Power BI | Microsoft Learn
Email subscriptions for reports and dashboards in the Power BI service - Power BI | Microsoft Learn
Solved: Subscription error - Microsoft Fabric Community
How to Get Your Question Answered Quickly
If it does not help, please provide more details.
Best Regards
Community Support Team _ RongtieIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- pvuppala
Helper V
Yes, this is a premium workspace and I made sure there are no nulls and the email fields is text field but still unable to setup the dynamic subscription. Has anyone been able to ?
- RodolfoC
Microsoft Employee
Hello pvuppala ,
This is a known bug that the team is already working on. We've seen it happen exclusively to WebAuthored reports so there's a couple of workarounds to this issue:
- The simplest is to try using FireFox, somehow this issue did not repro in that browser.
- You can open the WebAuthored report in ReportBuilder, save it, and republish it. I believe ReportBuilder strips the file of WebAuthored metadata and should no longer run into this issue.
Hopefully one of these alternatives is available to you.