About BrunoMueller

BrunoMueller · ‎01-20-2021

Editor's note (10/9/23): This blog post provides additional context and help. This message often comes from incompatible encoding between your SAS dataset and the SAS encoding. Use Proc CONTENTS on your input dataset to see the encoding used and see how it compares to your current SAS encoding. To display the SAS encoding use: proc options option=encoding define; run; To be able to read the data anyway, you can use the following code: data newdata; set olddata(encoding=any); run; Please be aware, that the chars that could not be converted will leave you with some strange text. If you know the encoding of the SAS datasets you can use the KPROPDATA function to convert it like so: data newdata; set olddata(encoding=any); str = KPROPDATA(v1, "UESC", "UTF-8"); run;

BrunoMueller · ‎01-18-2021

Add the NOCOMPLETECOLS to the Proc REPORT statement

BrunoMueller · ‎11-30-2020

I assume you want to do this in a Visual Analytics Report, is that right? If so, I would move to the Visual Analytics board. Please have a look at this post https://communities.sas.com/t5/SAS-Communities-Library/Calculating-First-and-Last-Days-of-the-Current-and-Future-Months/ta-p/307993 by @Renato_sas. He explains on how to calculate the dates your are after. To save you some time, here is the formula to calculate n months from "now" DateFromMDY(( ( ( Month('now - date'n) + ( 'n_months'p - 1 ) + 1200 ) Mod 12 ) + 1 ), 1, ( ( Year('now - date'n) + Trunc(( (Month('now - date'n) + ( 'n_months'p - 1 ) + 1200 ) / 12 )) ) -100 )) Please note, this expression is using "now - date" (datepart of now) and a parameter named n_months. I used the parameter for testing purposes, -n to go n months back, +n to go n months forward. Some other examples, First of next month DateFromMDY(( ( Month('now - date'n) Mod 12 ) + 1 ), 1, ( Year('now - date'n) + Trunc(( Month('now - date'n) / 12 )) )) Last day of current month, makes use of previous result TreatAs(_Date_, ( TreatAs(_Number_, 'first_of_next_month'n) - 1 ))

BrunoMueller · ‎11-20-2020

Yes it can. As you can see once the custom graph is used within a report you can change the colors, set the green to white and it will look like this: Please note, that when you do make changes to your custom graph template you need to recreate it in the report. This example is using the SASHELP.CARS data. The Y axis of the line is using the average or Horsepower, the two measures used in the bar chart are calculated as described above.

BrunoMueller · ‎11-12-2020

Yes weight= will multiply the original value with the weight value. You can not use an alias (ls2) in the weight= option it has to be a proper variable. The example provided by @Kurt_Bremser does exactly what you need. Please note it is using the MEAN statistic, as this is what you need.

BrunoMueller · ‎11-11-2020

Have a look at the following example. To use a weight on a variable, it has to be a variable in the input data set. So I created a second variable load_sum2 that has the same content as loan_sum. Both variables are used in the report using an alias ls and ls2. LS2 is using the weight= option. This gives us the two different totals plain and weighted. We then have a third computed column that uses the two LS... values to computed the number you are looking for. In the DEFINE statement we can use the NOPRINT option to suppress the printing. Give it a try: data have; input Customer_ID Team $ Loan_Sum interest_rate; Loan_Sum2 = Loan_Sum; cards; 111 A 100 2 333 A 200 3 888 A 300 4 222 A 400 5 111 B 300 6 777 B 400 2 333 B 100 3 ; proc report data=have; column Team Loan_Sum=ls loan_sum2=ls2 ls_wgt Customer_ID interest_rate; define Team / group; define ls / analysis sum format=comma12. "Loan SUM"; define ls2 / analysis sum weight=interest_rate format=comma12. "Loan SUM weight" /* noprint */ ; define ls_wgt / computed format=comma10.3 ; define Customer_ID / analysis N format=comma12. "Nr_Loans"; define interest_rate / analysis mean format=comma12.3 "Weighted_Avg_interest_rate"; compute ls_wgt; ls_wgt = ls2 / ls; endcomp; ; run;

BrunoMueller · ‎11-11-2020

The weight variable must be a variable in your input dataset

BrunoMueller · ‎11-04-2020

I ran this code on SAS Viya 3.5, it works every time, in the log one can see, that there is always a new file uri shown. filename reffile filesrvc folderpath="&exp_path" filename='cars.csv'; proc export data=sashelp.cars outfile=REFFILE dbms=csv replace ; run; What are your permissions on the folder you write the file too? You can view those using the applications menu -> Environment Manager -> Content and then use the RightMouseButton to view the Authorization on the folder in question. Maybe it is best to contact Technical Support on this error.

BrunoMueller · ‎11-02-2020

Please provide the sample code you run as well as the result you get, this will help to understand what you explain. Axis scaling and number of thick marks is done automatically depending on the data. There are ways to control this, using the YAXIS/YAXIS2 statements. Have a look at this blog for more information https://blogs.sas.com/content/graphicallyspeaking/2012/04/30/axis-values-and-hint/

BrunoMueller · ‎10-30-2020

The data and the program provided did not match, so I made some assumptions on how the variables might be used. I made some changes to your Proc SGPLOT, mainly removed double entries and corrected some typos. As a genral rule there is only one BY statement in a procedure. Always just start with the basics and add additional options as necessary. The following code should bring you close to what you want: data WORK.NEW1; infile datalines ; input Date:DATE9. cvar : $5. s_count : 8. _M_Count : 8.; format date date9.; datalines; 01MAR2020 00090 1941 3899 02MAR2020 00090 1938 3885 09MAR2020 00090 1933 3876 16MAR2020 00090 1933 3874 23MAR2020 00090 1936 3874 30MAR2020 00090 1936 3874 06APR2020 00090 1936 3868 13APR2020 00090 1936 3867 20APR2020 00090 1941 3868 27APR2020 00090 1941 3868 04MAY2020 00090 1942 3862 11MAY2020 00090 1943 3862 18MAY2020 00090 1939 3845 25MAY2020 00090 1940 3850 01MAR2020 00445 3965 7907 02MAR2020 00445 3970 7916 09MAR2020 00445 3979 7938 16MAR2020 00445 3985 7951 23MAR2020 00445 3991 7967 30MAR2020 00445 4001 7989 06APR2020 00445 3936 7855 13APR2020 00445 3944 7869 20APR2020 00445 3954 7881 27APR2020 00445 3969 7905 04MAY2020 00445 3915 7802 11MAY2020 00445 3924 7814 18MAY2020 00445 3936 7832 25MAY2020 00445 3940 7836 ; ods excel file="c:\temp\results.xlsx" options( sheet_interval='BYGROUP' sheet_label='prefix' ) ; proc sgplot data=new1 noborder; by cvar; styleattrs datacolors=(red blue); /* xaxis type=discrete;*/ /* Y2AXIS TYPE=DISCRETE;*/ series x=date y=s_count / datalabel legendlabel = 'SCount' ; series x=date y=_M_Count / datalabel legendlabel = 'MCount' y2axis ; xaxis interval=MONTH label=' ' valuesformat=MONYY7.; yaxis label = "Acc Count " display=(noline) grid; y2axis label = "Member Count " display=(noline) grid; run; ods excel close;

BrunoMueller · ‎10-23-2020

It seems that currently there is not a simple way to have CAS Formats available as SAS Formats. The is the sessionProp.listFmtRanges action that will list the range definitions, this can be saved to a SAS data set. You still need some logic to make a SAS format out of it. Here is a sample to write the result of sessionProp.listFmtRanges to a SAS data set: cas sugus sessopts=(caslib="casuser"); proc cas; action sessionProp.listFmtRanges result=results / fmtlibname="userfmtlib"; saveresult results dataout=work.fmt; run; quit;

BrunoMueller · ‎10-19-2020

Maybe you look at a crossing, where there is not data so it is displayed as missing. Which version of VA are you using? Newer versions of VA display the "no data" condition differently, see image below:

BrunoMueller · ‎10-19-2020

If your code or data is stored in the SAS Content/SAS Folder tree, then you can use the FILESRVC file access method. See here for an example: https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=lestmtsglobal&docsetTarget=p0qapul7pyz9hmn0zfoefj0c278a.htm&locale=en#n0jkbbdvak6hann1og91a9o280rh

BrunoMueller · ‎10-15-2020

Yatin I suggest to open a new discussion and provide your code sample with the log, this will help. Thanks

BrunoMueller · ‎10-02-2020

If you DATA Step runs on the SAS Compute Server, then the formats used, must be available as a SAS Catalog entry. Proc FORMAT will be default always create a format as a SAS catalog entry, default catalog is WORK.FORMATS. Formats that are available as a CAS format library are not available to the SAS Compute Server. In short: formats can/must exist in two locations, depending on how they are used: on the SAS side in a SAS Catalog on the CAS Server side as CAS Format Library Hope this information helps

Online Status	Offline
Date Last Visited	‎12-17-2025 09:19 AM