BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.

Hi,

As I understand it, when Web Report Studio (WRS) invokes a stored process, the only output format it can receive from the stored process is the SASREPORT (xml) format. Is that correct?  And also, it looks like WRS can only receive PACKAGE results, not streaming results?

The implication of this is that if I have a stored procedure, and want the user to be able to specify _ODSDEST= pdf | rtf | html, the user CANNOT use WRS to invoke the stored procedure, because WRS is only happy receiving _ODSDEST=SASREPORT. Correct?

So basically, WRS can receive (and create, and store, and edit) reports in this SASREPORT (xml) format.  And that is really the only file format "supported" by WRS.  (with I guess exception that if you register a pdf, looks like its possible for WRS to display it, and could create a pdf through "print" command).

Thanks,

--Q.


The Boston Area SAS Users Group (BASUG) is hosting an in person Meeting & Training on June 27!
Full details and registration info at https://www.basug.org/events.
1 ACCEPTED SOLUTION

Accepted Solutions
Cynthia_sas
Diamond | Level 26

Hi:

  Essentially, this understanding is correct. SAS Web Report Studio is "geared" to use SAS Report XML as the format for the reports which it displays inside the WRS interface. "Streaming" results are sent to a client browser using the HTTP protocol -- since WRS runs under the control of a Java-based application, it does not communicate using the HTTP protocol to receive results from a stored process.

  The nice thing about creating a stored process with package results, in general, is that with package results, you can put multiple outputs into the package (conceptually like a zip archive) and then you could publish the package to a webDAV repository or email the result package or send the package to a client application that knows how to deal with the package.

  Suggest you read the Stored Process Developer's guide for more thorough info.

cynthia

View solution in original post

2 REPLIES 2
Cynthia_sas
Diamond | Level 26

Hi:

  Essentially, this understanding is correct. SAS Web Report Studio is "geared" to use SAS Report XML as the format for the reports which it displays inside the WRS interface. "Streaming" results are sent to a client browser using the HTTP protocol -- since WRS runs under the control of a Java-based application, it does not communicate using the HTTP protocol to receive results from a stored process.

  The nice thing about creating a stored process with package results, in general, is that with package results, you can put multiple outputs into the package (conceptually like a zip archive) and then you could publish the package to a webDAV repository or email the result package or send the package to a client application that knows how to deal with the package.

  Suggest you read the Stored Process Developer's guide for more thorough info.

cynthia

Quentin
Super User

Thanks Cynthia!

Took me a while to figure out why my stored process which ran fine under SPWA was not returning results (or errors) when I ran it from WRS.  Then luckily I happened to try _odsdest=SASREPORT, everything appeared, and I started reading up on what might be going on.... Very much appreciate your response.

-Q.

The Boston Area SAS Users Group (BASUG) is hosting an in person Meeting & Training on June 27!
Full details and registration info at https://www.basug.org/events.

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 2 replies
  • 1533 views
  • 0 likes
  • 2 in conversation