I would suggest ODS and PROC DOCUMENT to get the Table of Contents you described. Here's sample code, a screen shot of my contents= file, and a link to a paper on the subject in case it's helpful: ods html file="before.html" contents="beforec.html" path="c:\temp"; ods document name=TOCtest(write); proc sgplot data=sashelp.class; vbar age / response=height; run; quit; proc sgpanel data=sashelp.class; panelby age / novarname columns=1; where age=15; hbar height; run; ods html close; ods document close; /* adjust the default style to enhance the table of contents */ /* here we remove the roman numeral in front of the first node */ ods path (prepend) work.template(update); proc template; define style styles.test; parent=styles.htmlblue; style contentProcname from Indexprocname / bullet=none; end; run; ods listing; proc document name=TOCtest; list / levels=all; run; make \test; dir \test#1; setlabel \test#1 "First Node"; setlabel \SGPlot#1\SGPlot#1 "First Output"; setlabel \SGPanel#1\SGPanel#1 "Second Output"; copy \SGPlot#1\SGPlot#1 to ^; copy \SGPanel#1\SGPanel#1 to ^; ods listing close; ods html file="after.html" contents="afterc.html" path="c:\temp" style=styles.test; replay \test#1; run; ods html close; quit; https://support.sas.com/resources/papers/proceedings11/252-2011.pdf ... View more

PROC TEMPLATE's CELLSTYLE AS can be helpful here, but you will need to code your ROW / COLUMN combinations in PROC TEMPLATE, not IML. Here's an example: ods path work.template(update) sashelp.tmplmst; proc template; define table Checkerboard; cellstyle _row_=2 && _col_=3 as data{backgroundcolor=yellow fontweight=bold }, _row_=4 && _col_=2 as data{backgroundcolor=yellow fontweight=bold }, _row_=5 && _col_=4 as data{backgroundcolor=yellow fontweight=bold }, 1 as data; end; run; ods trace on; proc iml; tbl = TableCreateFromDataSet("Sashelp", "Class"); IND = {2 3, 4 2, 5 4}; call TablePrint(tbl) numobs=6 template="Checkerboard" ; quit;   Here are my results from SAS 9.4m8:     ... View more

What results do you get, and do you see any errors or warnings in your .log file? Please post the contents of your log file and a screen shot of the results you're seeing which are incorrect.   ... View more

To address the following question:   Is there a way of uploading local file into Viya server, similar to this _Dataout way? Otherwise we have to use FTP tools to save to the server first, then use the proc import. It would be very helpful and convenient if a similar approach is available to upload local file directly into Viya / Studio server.   There is not an automated process that makes local files from your client PC available to the SAS Viya server. I suggest the following blog as a resource: https://blogs.sas.com/content/sgf/2022/02/14/where-are-the-files-that-you-have-access-to-through-sas-studio/ ..and if you have follow up questions I would be happy to address them via a tracking entry opened to Technical Support. This will help us have a direct dialog if I need more information about your Viya environment.  ... View more

If knowing which ODS destination is open is important then the following SASNote may prove useful: https://support.sas.com/kb/33/590.html   However, please note that PROC TRAJ is not a procedure developed, distributed, or supported by SAS Institute.  It is a user-written procedure available from a third party.  When asked about PROC TRAJ, we recommend customers do an internet search for it.  For questions, customers need to contact the author of that procedure directly for assistance. PROC TRAJ web page is    http://www.andrew.cmu.edu/user/bjones/ ... View more

I am not finding a way to control the scroll bars in SAS ® Studio but am happy to investigate if this feature is available via a SAS ® Viya ® configuration property or a change to a browser setting.    What version of SAS Viya are you running and what browser are you using? If you change the browser you use do you see a difference in the width of the scroll bars? Please also clarify: are the scroll bar widths in SAS Studio the same or different as those in SAS ®  Visual Analytics or another SAS Viya application? ... View more

Hey Randy!   The PDF destination does use the system option locale to define the language property in the PDF files created by ODS, whether the file is tagged or not.  I am not finding any way to override this, so if that is what you are looking to do, please update here or create a tracking entry for Tech Support and I'll be happy to ask the RnD team if there are any locations I missed (I checked the SAS registry and don't see it set there).   Have a great week! Bari ... View more

Hi Tom!   I don’t see the fileref _dataout officially documented either. It’s part of the (voluminous) precode that is generated by default by SAS Studio.   From SAS Studio 5.2 Enterprise, if I choose options..preferences. Under “code and log” I see “Show generated SAS code in the SAS log”:       With this preference enabled, when I submit any code from SAS Studio, I see the precode in the log (with filename _DATAOUT shown here at line 20):     So the existence of that fileref helps the code that you are showing create a file that is downloaded. Here's a doc reference I am finding on the macro variables _DATAOUT_MIME_TYPE &  _DATAOUT_NAME :   https://go.documentation.sas.com/doc/en/webeditorcdc/3.6/webeditorrepodg/n0303y7wu1a1myn13kuatdwnfqdy.htm Let me know if this helps and if there is more information you need. ... View more

I am sure you have found your answer by now, however someone reported this problem to Technical Support and referenced your communities post, so I'd like to share the following SASnote with others who may need the reference. When the LASTPAGE text shows incorrectly (ie with garbage characters), please try options printerpath=pdf ; as discussed in this SASnote:   http://support.sas.com/kb/56/041.html   If you continue to have difficulties, please always feel free to reach out to support@sas.com !         ... View more

I would suggest creating a unique identifier like this example shows, using _n_ : 22932 - How to use PROC TRANSPOSE to get one record per BY group With your data, it may be necessary to keep the _name_ variable from the first Transpose step, then create (with the DATA step) another variable in the data set FIRST for use on the ID statement in the second Transpose step. This new variable would have the values (from _name_): RelationshipN, ContactnameN. ... View more

If you are using PROC REPORT, I would suggest using COMPUTE AFTER logic with a LINE statement, or POSTTEXT like the sample code below shows.  If you are not using REPORT, you can use PROC TEMPLATE to get similar results. Notes/Caveats: pagination on the last page is NOT guaranteed, since observation counts can make this text flow to the next page. using POSTTEXT works on a TABLE basis, so if your PROC step paginates (PRINT/PAGEBY or REPORT with BY or break after group_order_var_here / page;) then the POSTTEXT text will repeat on each of these pages (ie TABLEs). only footnotes will sit at the very bottom of the PDF page. Newline or other inline commands can be used to move other text "down" on the page, but this will require knowing how many observations are on the last page. If you have followup questions, please email them to support@sas.com with your LOG and PDF file and we'll be happy to investigate further. ods escapechar="^"; proc template; define style mystyle;   parent=styles.printer;    style table from output /     posttext="^{style systemtitle NON REPORT table}"      frame=void rules=groups ; end; run; options nodate nonumber orientation=portrait; title "title"; footnote "footnote"; ods pdf file="c:\temp\not_report.pdf" notoc style=mystyle; proc print noobs data=sashelp.cars /*style(report)={frame=void rules=groups posttext="This is posttext"}*/ style(header)={background=white}; var origin make model; run; ods pdf close; options nodate nonumber orientation=portrait; title "title"; footnote "footnote"; ods pdf file="c:\temp\report.pdf" notoc; proc report nowd data=sashelp.cars style(report)={frame=void rules=groups posttext="^{style systemtitle This is posttext}"} style(header)={background=white} style(lines)=systemtitle; col origin make model; define origin / group; compute after ; line "Text to mimic footnote"; endcomp; run; ods pdf close; ... View more