Publish Report via API with Registered Resources

[BryanCarmichael]

Hi - new problem to solve 

Very familair with publishing reports from pbip structures via the Fabric API - however hit a new wrinkle.

Whenever you add a Registerd Resource e.g. an image and try and publish in this manner you get an error that the registered resource cannot be located.

Anyone encountered this and found a way around it or is it a known issue with no current resolution ?

Thanks in advance

[Anonymous · Accepted solution]

Hi @BryanCarmichael,

Thanks for reaching out to the Microsoft fabric community forum.

Yes, this is a known limitation when working with .pbip files that include registered resources like images. When publishing via the Fabric REST API, the API currently doesn't handle those registered resources properly evem though they’re included in the .pbip structure, the API doesn't resolve them during deployment. That’s why you're seeing the “resource cannot be located” error.

At the moment, there’s no official support or workaround through the API for this. The safest options for now are eitheravoid using registered resources in .pbip files you plan to deploy via API, or publish the report directly from Power BI Desktop, which handles the resource references correctly.

Hopefully this is something that gets addressed in a future update, but as of now, this behavior is expected.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[Poojara_D12 · Accepted solution]

Hi @BryanCarmichael 

What you’re encountering when publishing reports that include Registered Resources—such as images—via the Microsoft Fabric API is a known limitation or current gap in support. Although the Fabric API allows publishing of reports and datasets programmatically, Registered Resources like images or other embedded assets often require additional handling because the API does not automatically upload or reference these resources alongside the report content. As a result, when the report tries to load these Registered Resources, it cannot locate them, causing the error you described. This is a fairly common issue, especially in newer or evolving APIs where resource management is still being improved. Currently, there isn’t a fully streamlined way to package and publish Registered Resources together with the report via the API in one step. Workarounds typically involve manually uploading these resources separately to the appropriate location (e.g., a content library or resource storage in the Power BI or Fabric service) before publishing the report, or embedding images directly within the report if possible. Until Microsoft enhances the API to support Registered Resources natively during publishing, you may need to continue using such manual steps or alternative workflows to avoid this error.

[Anonymous · Accepted solution]

Hi @BryanCarmichael,

Thanks for reaching out to the Microsoft fabric community forum.

Yes, this is a known limitation when working with .pbip files that include registered resources like images. When publishing via the Fabric REST API, the API currently doesn't handle those registered resources properly evem though they’re included in the .pbip structure, the API doesn't resolve them during deployment. That’s why you're seeing the “resource cannot be located” error.

At the moment, there’s no official support or workaround through the API for this. The safest options for now are eitheravoid using registered resources in .pbip files you plan to deploy via API, or publish the report directly from Power BI Desktop, which handles the resource references correctly.

Hopefully this is something that gets addressed in a future update, but as of now, this behavior is expected.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[Anonymous]

Hi @BryanCarmichael,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.

If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

[Anonymous]

Hi @BryanCarmichael,
Hope everything’s going smoothly on your end. We haven’t heard back from you, so I wanted to check if the issue got sorted. If yes, marking the solution would be awesome for others who might run into the same thing.
Still stuck? No worries just drop us a message and we can jump back in on the issue.

Thank you 

[Anonymous]

Hi @BryanCarmichael,
I just wanted to follow up on your thread. If the issue is resolved, it would be great if you could mark the solution so other community members facing similar issues can benefit too.
If not, don’t hesitate to reach out, we’re happy to keep working with you on this. 

Best Regards,

Hammad.