Forum Discussion
PowerBI Dashboard Embed iframe src Circular structure console error
- 1 year ago
Hi KCChan,
Thanks for the follow-up and for confirming that you have already implemented deep cloning and updated to the latest Power BI client version.
Since the issue is still occurring intermittently, it is possible that certain elements in the runtime environment such as Angular-specific services, observables, or context-bound callbacks might be unintentionally introducing circular references into your embed configuration. Here are a few suggestions to help further isolate the issue:
- Create a fresh embedConfig object for each embed attempt, especially after rerenders.
- Avoid passing Angular services or zone related logic directly into the embed configuration or event handlers, as these may introduce hidden circular references.
- Ensure that the embed logic only runs after the component view is fully initialized, in line with Angular lifecycle best practices.
- If you’re using a custom wrapper for the embedding logic, double-check for side effects or reused references that could be contributing to the problem.
If you've reviewed all the above and the issue still persists especially given that your stack trace points to Power BI SDK internals it would be a good idea to How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn This will allow the engineering team to investigate further and provide a more targeted resolution.
If this post helps, please give it a thumbs up Kudos and consider marking it as a solution so it can assist other community members as well.
Thank you for using the Microsoft Community Forum.
I’ve tried the recommended approach, including updating to the latest version of the powerbi-client package and ensuring that the dashboard viewer options are correctly parsed. Unfortunately, the issue still occurs intermittently.
const clonedOptions = JSON.parse(JSON.stringify(plainOptions));
this.dashboardViewerOptions = clonedOptions;The issue appears to originate within the Power BI script, where a circular object is being passed and causes the JSON to be rejected.
Hi KCChan,
Thanks for the follow-up and for confirming that you have already implemented deep cloning and updated to the latest Power BI client version.
Since the issue is still occurring intermittently, it is possible that certain elements in the runtime environment such as Angular-specific services, observables, or context-bound callbacks might be unintentionally introducing circular references into your embed configuration. Here are a few suggestions to help further isolate the issue:
- Create a fresh embedConfig object for each embed attempt, especially after rerenders.
- Avoid passing Angular services or zone related logic directly into the embed configuration or event handlers, as these may introduce hidden circular references.
- Ensure that the embed logic only runs after the component view is fully initialized, in line with Angular lifecycle best practices.
- If you’re using a custom wrapper for the embedding logic, double-check for side effects or reused references that could be contributing to the problem.
If you've reviewed all the above and the issue still persists especially given that your stack trace points to Power BI SDK internals it would be a good idea to How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn This will allow the engineering team to investigate further and provide a more targeted resolution.
If this post helps, please give it a thumbs up Kudos and consider marking it as a solution so it can assist other community members as well.
Thank you for using the Microsoft Community Forum.
- v-kpoloju-msft1 year agoCommunity Support
Hi KCChan ,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participation.