This doesn't sound like a script that can be performed on the server. Scripts performed on the server perform from a different context than that seen for the client where Perform Script On Server was used to perform that script in a Server context. You can pass data to the script in a script parameter and get data back in a script result, but you can't see a found set pulled up on a layout via that server performed script--and that would be a typical result of using a script to generate a report.
Note, however, that if your script creates a series of new records, a find performed on the client machine can pull them up in a found set.
Report An Issue is intended for Reporting Possible Software bugs. Questions on how to work with FileMaker Pro should be posted in the FM Pro Forum Section. (See tab at top of this screen.)
It's unfortunate that it works that way. I was trying to speed up the generation of a report that takes about five minutes to run when interacting with the server. . If all the finding and sorting could be done on the server and then downloaded to the report it would probably run much quicker. This same report takes less than a couple of seconds to run if I use a copy of the data base that's on my computer instead
Yes, I would like to see the number of server compatible script steps increased. In particular, I'd like to see Save As PDF become a server compatible script step as a server side script could then generate the report as a PDF and insert it into a container field that the originating client could then find and view/open/print...