I am hitting the same issue. It looks like inside the module, it specifically requests the module name and screen name:

    var location = window.UltimatePDF.runtime.getLocation();
    var paths = location.pathname.substr(1).split("/");
    $parameters.Module = paths[0];
    $parameters.Screen = paths[1];
    if (location.search) {    $parameters.QueryParameters = location.search.substr(1);}

I even tried to do a custom URL so that instead of /ActionPDF, it would be /MyPage/ActionPDF, but it printed the screen instead of rendering the page that I had created.

Hi. This is indeed not working at the moment.

As a workaround, don't use the ScreenToPDF block, and instead of navigating to the report screen, you can call a server action that executes the PrintToPDF action with the URL of the report screen. Make sure you choose a suitable timeout value for this server action.

This issue has been fixed in version 9.0.5.

Thanks for your solution. 

But the workaround solution not work. So, we are planning to upgrade this component 9.0.0 to version 9.0.5 . 

Regards,

Another, albeit not great, workaround is to use JavaScript (due to a know issue with Reactive web redirects). You reformat the URL with <hostname>/<modulename>/<pdfscreen>?<parameters> and have JavaScript either replace the URL or open a new tab. Not sure on the 9.0.5 compatibility though.

Hi, it's me again. 

After we upgrade to 9.0.5 but no luck, it's another error on SEO URL (the default URL still good)

https://<modulename>.company.com/<screenname>?param: Could not locate deployment zone based on module name: <screenname>"

So, component still thinking that our <screenname> is module.

Could you please check this.

Regards,

TriDP

Hi Phouc.

Are you using ScreenToPDF block, then navigating to the screen from your application? I tested that scenario before I released version 9.0.5.

Could you try using the URL https://<modulename>.company.com/<modulename>/<screenname> so that it will keep using the same site?