Issue with Frontend Server Setup – "Empty iframeId" Error in Workload Development Kit

[Ashwath_Bala_S]

Hi Team,
We are currently setting up the local development environment by following the instructions provided in the Workload Development Kit documentation.

However, when attempting to run the frontend server, we encounter the following error in the console: 
workload-client.js:608 Uncaught (in promise) Error: Empty iframeId

Could you please help us understand the cause of this issue and guide us on how to resolve it?

Note: See attached screenshot of the error

Thank you in advance for your support.

[DigambarKangude]

Hi Team,

I also facing same issue. 

I have configured front-end and backend as mentioned into Workload development kit document and working fine but while start front-end app (React) It gives error as mentioned into attached file

Thank you in advance for your support.

[v-achippa]

Hi @Ashwath_Bala_S,

Thank you for reaching out to Microsoft Fabric Community.

Could you please confirm whether this frontend workload you are developing using the Workload Development Kit (WDK) is intended to integrate with Microsoft Fabric or Power BI, like for example as a custom visual, data app or OneLake extension?

Or is it part of a different Microsoft 365 platform such as Microsoft Teams or another M365 workload?

This will help us provide the most accurate solution to the issue.

Thanks and regards,

Anjan Kumar Chippa

[Ashwath_Bala_S]

Hi @v-achippa,

Yes, this workload we are developing is using the Workload Development Kit (WDK) which is intended to

integrate with Power BI custom visuals and data

[v-achippa]

Hi @Ashwath_Bala_S,

Thank you for confirming that you are using the WDK to build a workload that integrates with power bi.

The error here likely occurs when the frontend is run outside of the expected WDK host environment and the SDK is unable to retrieve the iframeId needed for initialization and context. Please follow below steps:

• Do not run the frontend directly in the browser, make sure you are launching your app through the WDK host or simulator, rather than directly accessing it from the browser.
• Ensure that your frontend code includes an initialize() call from the SDK like somewhere in the startup code this should present. This ensures the SDK receives context values like iframeId.

If this post helps in resolving the issue, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Ashwath_Bala_S,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Ashwath_Bala_S,

We wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Ashwath_Bala_S,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa