Based on your results and what @Kurt_Bremser wrote there are no differences for the rows with matching ID's but there are 2103 rows that don't match over the ID variables highly likely caused by some very small differences in at least one of these ID variables.   You could first round numerical variables to some non-significant decimal place before the comparison using code as below. data work.&ordsn; set ordata.&ordsn; array _numvars _numeric_; do over _numvars; _numvars=round(_numvars,0.00000000001); end; run; data work.&snowdsn; set snowdata.&snowdsn; array _numvars _numeric_; do over _numvars; _numvars=round(_numvars,0.00000000001); end; run; title "ordata.&ordsn versus &snowdsn"; proc compare base=work.&ordsn compare=work.&snowdsn Criterion=0.000000001 fuzz=.001 out=result listobs outbase outcomp outdif outnoequal maxprint=50; id member medicaid_no claim_number line_number PAY_DT F_DOS L_DOS DOS AMT_REQ QTY ; attrib _all_ label=''; format _all_; informat _all_; run; ... View more

@pavank Nothing wrong with your code but there are of course almost always a multitude of coding options. Here one more: data want; set have; length left_to_right right_to_left $5; keep left_to_right right_to_left; left_to_right=catx(' ',first(name),first(gender),first(city)); right_to_left=reverse(left_to_right);; run;   ... View more

Before using any macro language to make things dynamic one should always first get some static code working.   You need first below to work. I would for the first iteration even replace the macro variables with hard coded strings in your code.  %let api_url=url; %let prompt=Player1; filename json_in temp; data _null_; file in; put "{ ""username"":""&prompt"" }" ; run; filename resp temp; proc http method="POST" url="&api_url ct="application/json" in=json_in out=resp; headers "Content-Type"="application/json"; run; Very first issue are unbalanced quotation marks url="&api_url ct="application/json" Also ensure that there aren't any problematic characters in your URL. Ideally use SAS function urlencode() to create a url that won't cause issues. ... View more

@StephenFoerster  Comment to section 3. De-Duplication: Nicholas Robert's article was written for Viya 3.3. There exists in-between now the specialized action deduplication.deduplicate.  With source and target table in CAS Proc Sort Nodupkey translates to action deduplication.deduplicate.  What this means: One can continue to use the good old and simple Proc Sort Nodupkey syntax and it will get mapped to the specialized action if possible.   ... View more

Your 2nd options sounds like something that should work. data have; document_date='25Feb2024'd; run; proc sql; select document_date ,document_date as document_date_2 format=date9. ,document_date as document_date_3 format=year4. from have ; quit;   ... View more

Are you changing the source file for the sole person of import into a SAS table? If that's the case then below code to directly read your source file into a SAS table. %let source=c:\temp\IMPORT_DATA.csv; data work.out; infile "&source" lrecl=500 dlm=',' truncover dsd; input @; _infile_=compress(_infile_,"|"); input var_1 : mmddyy8. var_2 : best32. var_3 : $3. var_4 : $300. var_5 : mmddyy8. var_6 : best32. var_7 : datetime30. var_8 : best32. var_9 : datetime30. var_10 : mmddyy8. ; format var_1 date9. var_5 date9. var_7 datetime30.6 var_9 datetime30.6 var_10 date9. ; run; ... View more

...and below how you could call the macro in case Region contains a comma separated list of values. /*real file will come from an Excel import*/ data driver; input if_statement $ 1-36 Region $ 37-60; datalines; if Make = 'BMW' then TEST2 = 'OK' 'Asia','USA' if Make = 'Ford' then TEST3 = 'OK' 'USA' 'Asia' if Make = 'Audi' then TEST1 = 'OK' 'Europe' 'Asia' 'USA' ; run; %macro makereport(Var=, Check=); data OUTPUT ; set SASHELP.CARS; where Origin IN (&Check); &Var; run; %mend makereport; data _null_; set driver; *builds string to execute macro; str = catt('%makereport(Var=',if_statement,',Check=%nrbquote(',Region,'));'); *execute macro; call execute(str); run; ... View more

@angel17th  I believe you could simplify your current code using syntax like below. data _null_; infile original; file fixed termstr=crlf; input; _infile_=tranwrd(_infile_,'"','""'); _infile_=tranwrd(_infile_,'|','"'); put _infile_; run; ... View more

csv files are just textual and can't store information like data types. When using Proc Import SAS will guess the data type based on the text if finds in the .csv ....and this is why you will find many discussions here where people state that you need to use a SAS data step with Infile/Input to have full control over how textual data gets mapped into SAS variables.  Only "lazy" way to write such a data step: Use Proc Import (or the EG/Studio import wizard) and then copy/paste the generated data step code into a code window and amend it to what you really need.   I never tried it but it might be possible that if you create a .csv with your numbers in double quotes then SAS will import them a strings. ...but again: Writing your own data step to read the data will lead to much more stable and predictable outcomes. ... View more

If you're already using a SAS supplied format like percent. below sample code to demonstrate how you can extend it for a missing case. proc format; value missToUnknown . = 'Unknown' other=[percent.] ; run; data demo; do var=-0.5,.,0,0.5; output; end; run; proc print data=demo; format var missToUnknown.; run;   ... View more

@angel17th Your code works as it should in my Windows environment. Are you sure this is not just a display issue? When I opened the generated file with Notepad++ and Word Wrapping selected I've seen exactly the same as you shared. But even though the 2nd record gets displayed on two lines it's still a single record (one CRLF).  And here some code to compare source with target that also confirms that things appear to work as desired. %let source=c:\temp\IMPORT_DATA.csv; %let target=c:\temp\FIXED_IMPORT_DATA.csv; filename original "&source"; filename fixed "&target"; data _null_; infile original lrecl=1 recfm=f ; file fixed termstr=crlf; input char $char1.; numpipe + (char='|'); if char='0D'x then return; else if char='0A'x then do; if mod(numpipe,2)=1 then put '|' @; else do; numpipe=0; put; end; end; else if char='|' then put '"' @; else if char='"' then put '""' @; else put char $char1. @; run; data source; infile "&source" truncover; input line:$1000.; run; data target; infile "&target" truncover; input line:$1000.; line=translate(line,'|','"'); run; proc compare data=source comp=target; run;   ... View more

@CathyVI wrote: @Patrick  How can anyone with a value of 1 be counted as a single case. For example row 33 in our data. When form2=2,case32=0 and event46=1, the report_form_name should be Event46A instead of multiple.    Anyone with 2 double digits e.g., 110, 220 should remain as multiple.   So now it's about counting cases and no more forms which totally changes the story! How would you want to report cases 112, 121, 211, 122, 212, 221? Please be specific and define all your cases. Provide both the variable they should appear under AND the time slot if there are multiple.   It would help if you could provide below table fully populated. With this data one can create formats which then should make the rest of the coding rather simple. Multiple patterns can of course belong to the same case (case_no). It would then also help if you provide sample data for all the patterns. Obs pattern case_no time_slot description 1 000       2 001       3 002       4 010       5 011       6 012       7 020       8 021       9 022       10 100       11 101       12 102       13 110       14 111       15 112       16 120       17 121       18 122       19 200       20 201       21 202       22 210       23 211       24 212       25 220       26 221       27 222         ... View more

To display missings as zero just use: options missing='0';   ... View more