About BrunoMueller

BrunoMueller · ‎02-12-2015

Find below your code with some additional statements to get the values between tags and get the tag name, it might be a starting point. Writing the XML to a file and then use the XML libname engine with a MAP file is maybe a lot more flexible and less code maintenance. You could add a key defintion to the XML string, so that you later can join the original data with the data read from the XML file. /* * this regular expression should match any XML tag * minimum length of tag is 2 /(<.[^(><.)]+>)/ */ data have; length notes $ 32767; notes = '<notes><aa>aacaa</aa><note><date domain="SVR_DATETIME">20140926T113458</date><timeZone>Pacific/Auckland</timeZone><author username="">Jane Doe</author><content>Note One Content Here</content></note><note><date domain="SVR_DATETIME">20141030T133030</date><timeZone>Pacific/Auckland</timeZone><author username="">Joe Bloggs</author><content>Note Two Content In Here</content></note><note><date domain="SVR_DATETIME">20141117T135213</date><timeZone>New Zealand Standard Time</timeZone><author username="">Joe Public</author><content>Note Three yada yada</content></note><note><date domain="SVR_DATETIME">20141117T152544</date><timeZone>New Zealand Standard Time</timeZone><author username="">Sally Citizen</author><content>Note4 Could be really long</content></note></notes>'; * notes = '<notes displayAsDescending="yes" showtimezone="no"><note><date domain="SVR_DATETIME">20140926T113458</date><timeZone>Pacific/Auckland</timeZone><author username="">Jane Doe</author><content>Note One Content Here</content></note><note><date domain="SVR_DATETIME">20141030T133030</date><timeZone>Pacific/Auckland</timeZone><author username="">Joe Bloggs</author><content>Note Two Content In Here</content></note><note><date domain="SVR_DATETIME">20141117T135213</date><timeZone>New Zealand Standard Time</timeZone><author username="">Joe Public</author><content>Note Three yada yada</content></note><note><date domain="SVR_DATETIME">20141117T152544</date><timeZone>New Zealand Standard Time</timeZone><author username="">Sally Citizen</author><content>Note4 Could be really long</content></note></notes>'; regxID = prxparse('/(<.[^(><.)]+>)/'); start = 1; stop = length(notes); call prxnext(regxID, start, stop, notes, position, length); prior_position = 1; do while (position > 0); tag = prxposn(regxID, 1, notes); prevPos = prior_position; prior_position = position + length; endTag = ( tag =: "</" ); if endTag = 1 then do; valueLen = position - prevPos; if valueLen > 0 then do; length tagValue $ 128; tagValue = substr(notes, prevPos, valueLen); tagName = scan(tag, 2, "/>"); end; end; output; call missing( valueLen, tagValue, tagName ); call prxnext(regxID, start, stop, notes, position, length); end; run;

BrunoMueller · ‎02-11-2015

Colors from styles can be referenced within STYLE= options, see the following example below: proc report data=sashelp.class; column _all_ _dummy; define _dummy / computed; compute _dummy / char length=128; row+1; if row > 10 then do; row=1; end; length gdataName $ 32; gdataName = cats('gdata', row); length styleDef $ 128; styleDef = cats( "style={background=GraphColors('" , gdataName , "')}" ); _dummy = styleDef; * call define(_row_, "style", "style={background=GraphColors('gdata1')}"); call define(_row_, "style", styleDef ); endcomp; run;

BrunoMueller · ‎02-11-2015

You can get to the source of a style using proc template ; source styles.htmlblue / EXPAND FILE=""; run; the EXPAND option will also print the definitions of the parent styles. the one can read in the file and look for color definitions, that might look like: 'gcdata4' = cx543005 'gdata4' = cxA9865B 'gcdata3' = cx01665E 'gdata3' = cx66A5A0 'gcdata2' = cxA23A2E 'gdata2' = cxD05B5B 'gcdata1' = cx445694 'gdata1' = cx6F7EB3;

BrunoMueller · ‎02-11-2015

Habe das Anliegen, Autocomplete für Variable Namen ausschalten, an die Entwickler weitergeleitet. R&D wird diese Anfrage prüfen, und wenn möglich in einer der nächsten SAS Enterprise Guide Version einbauen.

BrunoMueller · ‎02-06-2015

You can use Proc REPORT to get the output you need. You can make use of the computed column functionality: < data have; infile cards dlm=","; input year x y ; cards; 2010,10,5 2011,23,6 2012,25,2 2013,20,4 2014,17,8 ; proc report data=have nowindows; column year x y myPct; define year / display; define x / analysis; define y / analysis; define myPct / computed format=percent9.0; compute myPct; myPct = y.sum / x.sum; endcomp; rbreak after / summarize; run; /body>

BrunoMueller · ‎01-23-2015

I guess the easiest way is just to assume some constant value for the day, since as you pointed out, some days might not exist in the financial month. As suggested earlier, I would create the value for the financial date outside of VA. SAS provides the INTNX function, which allows you do advance a date by some interval, see the example below: data have; infile cards dlm=","; input saleDate : date9. amount : best12. ; fiscalDate = intnx("month", saleDate, 6, "B"); format saleDate fiscalDate date9.; cards; 30aug2014,123 31aug2014,456 ;

BrunoMueller · ‎01-22-2015

Please be aware the expression I used only works if the fiscal year starts on 01July. I suggest you add the fiscalDate column to the data that is loaded into the LASR Server.

BrunoMueller · ‎01-22-2015

However I think it is a lot easier to just copy/paste the expression in the text area, in picture above marked in red

BrunoMueller · ‎01-22-2015

I have used the follwoing expression to build the new fiscal year, this might help you get started IF ( Month('saleDate'n) BetweenInclusive(1, 6) ) RETURN DateFromMDY(( Month('saleDate'n) + 6 ), DayOfMonth('saleDate'n), ( Year('saleDate'n) + 0 )) ELSE DateFromMDY(( Month('saleDate'n) - 6 ), DayOfMonth('saleDate'n), ( Year('saleDate'n) + 1 ))

BrunoMueller · ‎01-22-2015

I suggest you build another date column, that has a proper date according to the finance year, for example your finance year begins on the 01jul2014 so you translate this into 01jan2015 and then use this new data item to build your YTD etc values. You will need to duplicate this new data item to get fiscal year and fiscal month (you can use the month format and display it as a number) to build a report, here is an example:

BrunoMueller · ‎01-22-2015

You can make use of the MOD option of the FILE statement, this will allow you to add new records to an existing external file. see this sample code, that illustrates this: * * create base file *; filename xbase temp; data _null_; set sashelp.class; where age lt 14; file xbase dsd dlm=","; put name age sex height weight; run; * * create append file *; filename xapp temp; data _null_; set sashelp.class; where age ge 14; file xapp dsd dlm=","; put name age sex height weight; run; * * use the base file with the MOD option, so * that new reords are appended to the file *; data _null_; file xbase mod; infile xapp; input; put _infile_; run; * * verify the result *; data _null_; infile xbase; input; putlog _infile_; run;

BrunoMueller · ‎01-21-2015

Habe selber keine Erfahrung damit, aber hier ein Artikel aus der SAS Community

BrunoMueller · ‎12-04-2014

Im SAS Enterprise Guide kann mit der rechten Maustaste "Copy HTML Source to the Clipboard" gewählt werden. Im Reply Fenster schaltet man dann auf HTML und kann so bequem the text aus dem Clipboard einfügen, Beispiel unten: options validvarname=v7; proc transpose data=have out=have_trsp; by flg stat commercial goal notsorted; var value; id date; idlabel date; run; Der Umweg über Word entfällt

BrunoMueller · ‎12-04-2014

Im SAS enterprise Guide kann mit der rechten Maustaste "Copy HTML Source to the Clipboard" gewählt werden. Im Reply Fenster schaltet man dann auf HTML und kann so bequem the text aus dem Clipboard einfügen, Beispiel unten: options validvarname=v7; proc transpose data=have out=have_trsp; by flg stat commercial goal notsorted; var value; id date; idlabel date; run; Der Umweg über Word entfällt

BrunoMueller · ‎11-28-2014

Since SAS Data Integration Studio produces SAS code, you can have a look at the examples in the documentation. They provide a good start. SAS(R) 9.4 Statements: Reference, Third Edition

Online Status	Offline
Date Last Visited	Wednesday