Hi,   Firstly, I know there are several posts on here (and the SAS website - https://support.sas.com/kb/31/278.html) detailing how to suppress the second node within a bookmark but every suggestion is not working.   I have a simple PROC REPORT, which will create a 1 page PDF. ods _all_ close; ods pdf file="C:/Myfile.pdf" pdftoc=1; ods proclabel="My Bookmark label"; proc report data=sashelp.cars contents=""; columns variable; break after variable / page contents=""; run; ods pdf close; ods listing;   Even with the PDFTOC=1 option and both CONTENTS="" I still see a 2 level bookmark in the PDF, first level = "My Bookmark label" and the second level = "Table 1".   Oddly when I set to the CONTENTS="AA" on the PROC REPORT line, in the PDF, I still see a 2 level bookmark, however the second level now has two entries "Table 1" and "AA". Am I missing something here, where is this "Table 1" coming from. My code does use other procedures (PROC MEANS and PROC MIXED) but these are defined outside the ODS PDF lines so should no no effect.   Running the SAS EG 8.3 application with SAS 9.4 M7.   Any help is greatly appreciated. ... View more

Hi,   I am trying to understand the XMLV2 LIBNAME engine. I have got the code to work with a custom XML map, but the dataset is empty.   My XML file: <?xml version="1.0" encoding="UTF-8"?> <ODM xmlns="http://www.cdisc.org/ns/odm/v1.3" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xmlns:nciodm="http://ncicb.nci.nih.gov/xml/odm/EVS/CDISC" xs:schemaLocation="http://www.nci.nih.gov/EVS/CDISC ../schema/controlledterminology1-0-0.xsd" FileType="Snapshot" FileOID="CDISC_CT.SDTM.2020-12-18" Granularity="Metadata" CreationDateTime="2020-12-17T14:45:28" AsOfDateTime="2020-12-18T00:00:00" ODMVersion="1.3.2" Originator="CDISC XML Technologies Team (Terminology2ODM converter)" SourceSystem="NCI Thesaurus" SourceSystemVersion="2020-12-18"> <Study OID="CDISC_CT.SDTM.2020-12-18"> <GlobalVariables> <StudyName>CDISC SDTM Controlled Terminology</StudyName> <StudyDescription>CDISC SDTM Controlled Terminology, 2020-12-18</StudyDescription> <ProtocolName>CDISC SDTM Controlled Terminology</ProtocolName> </GlobalVariables> <MetaDataVersion OID="CDISC_CT_MetaDataVersion.SDTM.2020-12-18" Name="CDISC SDTM Controlled Terminology" Description="CDISC SDTM Controlled Terminology, 2020-12-18"> <CodeList OID="CL.C66742.NY" Name="No Yes Response" DataType="text" nciodm:ExtCodeID="C66742" nciodm:CodeListExtensible="No"> <Description> <TranslatedText xml:lang="en">A term that is used to indicate a question with permissible values of yes/no/unknown/not applicable.</TranslatedText> </Description> <EnumeratedItem CodedValue="N" nciodm:ExtCodeID="C49487"> <nciodm:CDISCSynonym>No</nciodm:CDISCSynonym> <nciodm:CDISCDefinition>The non-affirmative response to a question. (NCI)</nciodm:CDISCDefinition> <nciodm:PreferredTerm>No</nciodm:PreferredTerm> </EnumeratedItem> <EnumeratedItem CodedValue="NA" nciodm:ExtCodeID="C48660"> <nciodm:CDISCSynonym>NA</nciodm:CDISCSynonym> <nciodm:CDISCSynonym>Not Applicable</nciodm:CDISCSynonym> <nciodm:CDISCDefinition>Determination of a value is not relevant in the current context. (NCI)</nciodm:CDISCDefinition> <nciodm:PreferredTerm>Not Applicable</nciodm:PreferredTerm> </EnumeratedItem> <EnumeratedItem CodedValue="U" nciodm:ExtCodeID="C17998"> <nciodm:CDISCSynonym>U</nciodm:CDISCSynonym> <nciodm:CDISCSynonym>UNK</nciodm:CDISCSynonym> <nciodm:CDISCSynonym>Unknown</nciodm:CDISCSynonym> <nciodm:CDISCDefinition>Not known, not observed, not recorded, or refused. (NCI)</nciodm:CDISCDefinition> <nciodm:PreferredTerm>Unknown</nciodm:PreferredTerm> </EnumeratedItem> <EnumeratedItem CodedValue="Y" nciodm:ExtCodeID="C49488"> <nciodm:CDISCSynonym>Yes</nciodm:CDISCSynonym> <nciodm:CDISCDefinition>The affirmative response to a question. (NCI)</nciodm:CDISCDefinition> <nciodm:PreferredTerm>Yes</nciodm:PreferredTerm> </EnumeratedItem> <nciodm:CDISCSubmissionValue>NY</nciodm:CDISCSubmissionValue> <nciodm:CDISCSynonym>No Yes Response</nciodm:CDISCSynonym> <nciodm:PreferredTerm>CDISC SDTM Yes No Unknown or Not Applicable Response Terminology</nciodm:PreferredTerm> </CodeList> </MetaDataVersion> </Study> </ODM> This is my XML map: <?xml version="1.0" encoding="UTF-8"?> <SXLEMAP version="1.2" name="SXLEMAP"> <TABLE name="EnumeratedItem"> <TABLE-DESCRIPTION>Terminology EnumeratedItem</TABLE-DESCRIPTION> <TABLE-PATH syntax="XPath"> /ODM/Study/MetaDataVersion/CodeList/EnumeratedItem </TABLE-PATH> <COLUMN name="CL_NAME"> <PATH syntax="XPath">/ODM/Study/MetaDataVersion/CodeList/@OID</PATH> <TYPE>character</TYPE> <DATATYPE>string</DATATYPE> <LENGTH>100</LENGTH> </COLUMN> </TABLE> </SXLEMAP> When I look at the IN library, I see the EnumeratedItems dataset, but it is empty. The log is clean, so not sure what I am missing.   This is the SAS code used filename in_map "C:\Documents\Example.map"; libname in xmlv2 "C:\Documents\Example.xml" xmlmap=in_map; ... View more

Hi,   I am using the PROC REPORT procedure with the #BYVAL dynamic function. The #BYVAL function works flawlessly in a TITLE statement, be in the output window in SAS or the PDF, RTF or HTML output. However, the #BYVAL function when used within a column header only works within the SAS output window and not the PDF, RFT or HTML output.   Below is same sample code which you should be able to copy and paste into your own SAS session: data input_data; do byvariable1 = 1 to 2 by 1; col1 = "XX (XX.X)"; col2 = "XX (XX.X)"; if byvariable1=1 then byvariable2 = "Female"; else if byvariable1=2 then byvariable2 = "Male"; if byvariable1=1 then do; header1 = "Some Text 1"; header2 = "Some Other Text 1"; end; else if byvariable1=2 then do; header1 = "Some Text 2"; header2 = "Some Other Text 2"; end; output; end; run; ods listing close; ods pdf file="%sysfunc(getoption(work))\test.pdf" nogtitle nogfootnote; proc report data = input_data split="|" nowd missing; column col1 col2; by byvariable1 byvariable2 header1 header2; define col1 / display "Header 1 #byval3"; define col2 / display "Header 2 #byval4"; title1 "#byval2"; run; ods pdf close; ods listing; Notice the COL1 and COL2 variables within the DEFINE statement within the PROC REPORT. I have included #BYVAL3 and #BYVAL4 in the column headers. Now, these do resolve to the correct values within the SAS output window. however, when I open the PDF document they simply say #BYVAL3 and #BYVAL4. Oddly though the #BYVAL2 line within the TITLE statement does appear correctly in both the SAS output window and the PDF output.   I am running SAS EG guide 7.15 on Windows 10. ... View more

Hi,    I am trying produce a figure using Graphic Template Language (GLT), however no matter what I try the fonts are not changing.   This is the PROC TEMPLATE code:   proc template; define statgraph series; begingraph / designwidth=800px designheight=500px border=false; layout datalattice rowvar=severity / headerborder=false columnaxisopts=(label="Visit" labelattrs=(family="courier new" weight=bold) tickvalueattrs=(family="courier new")) rowdatarange=union rowaxisopts=(label="Mean" labelattrs=(family="courier new" weight=bold) tickvalueattrs=(family="courier new")); ** Plot; layout prototype / cycleattrs=true; seriesplot x=xvar y=mean / name="mean" group=treatment; endlayout; ** Legend; sidebar / align=bottom; discretelegend "mean" / border=false valueattrs=(family="courier new" weight=bold); endsidebar; endlayout; endgraph; end; run;   I am setting the font for all components to Courier New yet once it runs and I open the output all components are using the Arial font. Any help? Sorry I cannot upload the actual output, but the log is also clean.   This is the code used to output the file: ods _all_ close; ods rtf file = "C:/Myfile.rtf" style=custom_style; ods graphics on / imagefmt = png; proc sgrender data = mydataset template = series; by myvariable; run; ods rtf close; ods listing;     ... View more

I am connecting a database using the LIBNAME statement, everything is working however it seems I am losing the labels and formats.    libname mylib db2 schema=myschema user=myusername using=mypassword; Any idea? ... View more