Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
There is an old, un-solved thread from 2019 on this issue, but this error continues to be thrown by all of my Power BI embedded reports today in the year 2022, so I'm re-posting in the hopes of shedding new light on this, since the previous thread was wholly ignored by any Microsoft staff.
The good news is that the error does not appear to prevent the report from successfully embedding.
All the same, every render of an embedded report is throwing this 'AI: StringValueTooLong' error in the console:
AI: StringValueTooLong message:"string value is too long. It has been truncated to 1024 characters." props:"{value:Error: Uncaught (in promise): SecurityError: Blocked a frame with origin \https://app.powerbi.com\ from accessing a cross-origin frame.\nError: Blocked a frame with origin \https://app.powerbi.com\ from accessing a cross-origin frame.\n at w.<anonymous> (https://content.powerapps.com/resource/powerbiwfe/scripts/reportEmbed.min.ed670225ef1b3fc0e30b.js:1:...n at https://content.powerapps.com/resource/powerbiwfe/scripts/reportEmbed.vendors.min.0229cae9c738c7d1c8...n at Object.next (https://content.powerapps.com/resource/powerbiwfe/scripts/reportEmbed.vendors.min.0229cae9c738c7d1c8...n at https://content.powerapps.com/resource/powerbiwfe/scripts/reportEmbed.vendors.min.0229cae9c738c7d1c8...n at new e (https://content.powerapps.com/resource/powerbiwfe/scripts/reportembed.externals.bundle.min.3823d8bc5...n at g (https://content.powerapps.com/resource/powerbiwfe/scripts/reportEmbed.vendors.min.0229cae9c738c7d1c8...n at w.isPerfRunnerRe}"
Can we get an update on this, and if there's anything to be done about it?
Thank you.
There were no recent changes to my project; I definitely didn't see this error previously. I'm not sure exactly when this error started showing up but it was within the last few days, and I didn't update my code during that time.
Based on some searching online, it seems pretty clear this error has been thrown in the past due to the dependency ApplicationInsight-JS (https://github.com/microsoft/ApplicationInsights-JS). Apparently when it first caused this error a few years back, it would crash report embedding altogether. I think the embedding-side got fixed so as to not crash, even if the error occurs; on the ApplicationInsight side, apparently some updates 'fixed' it a while ago, but then it reappeared again...and now in 2022 I'm clearly seeing it again. Whatever 'fixes' they are doing don't seem to last very long, it seems!
Hi @mholloway ,
It's a little difficult to find the cause of the problem only with the above error message... Whether your embedded reports get the same error before? Did you make any change on the reports? Any REST API involved in the report?
Best Regards
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |