Hi @Munyaradzi Kandoro !

Had the same problem in some projects i've worked, and the solution is simple.

Basically we are talking about Reactive Webs, that can change a value and the changes replicates in the page, but in this case, an component created by third parties that renders the PDF file, probably isn't capable of knowing that your file was retrieved from the server.

So what i recommend you to do is control better the lifecycle of the situation:

First: If you are loading the file from an data action, you can put an if in the pdf component at the screen, and inside that if you will create an condition to control the exibition when the Binary is loaded. You can use "NameOfYourDataAction.IsFethed = True", or if you want make it the logic more visible on the local action, create a local variable of type boolean that will control if you data was loaded, then change the value to true using the AfterFetch on your created DataAction using the assign option.

That way the PDF component will only be rendered after the binary is available.

Hope this help you!

Hello, I am having the exact same problem. Is there a solution already for this?