Create CODE SNIPPETS?? Can you clarify what that means. If you want to insert linebreak that it put the data into a FILE, not a macro variable. filename snippet temp; proc contents data=sashelp.class noprint out=contents; run; proc sort data=contents; by varnum; run; data _null_; file snippet; set contents end=eof; if _n_=1 then put @2 'columns=' / @4 '{' @; else put @4 ',' @; put '{' name= :$quote. label= :$quote. '}'; if eof then put @4 '},' ; run; Result: columns= {{NAME="Name" LABEL="" } ,{NAME="Sex" LABEL="" } ,{NAME="Age" LABEL="" } ,{NAME="Height" LABEL="" } ,{NAME="Weight" LABEL="" } }, ... View more

@SASJedi wrote: This turns out to be a problem with the SAS Online Docs. The use of data set options for loading a hash object is not supported in CAS. I've reached out to the documentation team and expect to see a note added to that effect in the next documentation update when it is published next month.   @acordes Based on above removing the data set options from your code should resolve the issue. %let mov_minutes1=10; %let mov_minutes2=30; %let incas=public; options mlogic symbolgen merror; data PUBLIC.X_TEST1(drop=_rc copies=0 replace=yes ); if _N_ = 1 then do; /* create variables */ if 0 then do; set CASUSER.TESTER1 PUBLIC._MOVE_BATCH3_TR(keep=name BATCH_ID movave3_batch movstd3_batch) PUBLIC._MOVE_MIN10_TR (keep=name movave10 movstd10 BATCH_ID datetime) PUBLIC._MOVE_MIN30_TR (keep=name movave30 movstd30 BATCH_ID datetime) ; end; /* define hash tables */ declare hash h_summary_a1(dataset: "&incas.._MOVE_BATCH3_TR"); h_summary_a1.defineKey('batch_id', 'name'); h_summary_a1.defineData('movave3_batch', 'movstd3_batch'); h_summary_a1.defineDone(); declare hash h_summary_a2(dataset: "&incas.._MOVE_MIN&mov_minutes1._TR"); h_summary_a2.defineKey('batch_id', 'name', 'datetime'); h_summary_a2.defineData("movave&mov_minutes1.", "movstd&mov_minutes1."); h_summary_a2.defineDone(); declare hash h_ndist_a2(dataset: "&&incas.._MOVE_MIN&mov_minutes2._TR"); h_ndist_a2.defineKey('batch_id', 'name', 'datetime'); h_ndist_a2.defineData("movave&mov_minutes2.", "movstd&mov_minutes2."); h_ndist_a2.defineDone(); end; call missing(of _all_); set CASUSER.TESTER1; /* lookup */ _name_=name; _rc = h_summary_a1.find(); _rc = h_summary_a2.find(); _rc = h_ndist_a2.find(); drop _name_; run; ... View more

Ahhh yep, that'll do it! That table was much bigger than it should've been. Always good to use varchar where possible to help with this! ... View more

I already use the append action, it works fine.  Only for sorting related calculations like first, last, lag, dif I use single mode, in all other cases it runs multi-threaded I think. Now with the delta load + ETL + append approach it runs fast. I have no worries about a 15 min frequency update.   ... View more

That fixes the problem Tom 🙂 ... View more

@acordes , hmm....I just had a colleague go through the process and it worked fine.    Did you modify your personal autoexec (by going to Options>Autoexec) and add the correct lines?  Can you check that those lines were saved to the autoexec?     It sounds like you might have called %test before the system option MAUTOLOCINDES  was set.  If that was the case, the definition for the macro test would have been added to work.sasmacr without the DESC field.  If you then set the system option and reran %test, the DESC will still be blank because the macro has already been added to the catalog.    The order is important in that  MAUTOLOCINDES  needs to be set before the first call to %test in order for the DESC to be added to the catalog and the dataset.     I would be happy to help you further through a technical support case if you need more assistance.  https://support.sas.com/en/technical-support.html   Regards, Grace    ... View more

Just for completeness. By putting the following initiation at the beginning of the execution, everything runs without problems.  I don't know why because later in the code and when needed I ensure that all caslibs are assigned. However, now it works.   Thanks to all @Patrick , @Tom , @BrunoMueller and @SASKiwi for pushing me towards the solution.   /* Init CAS library; */ cas mySession sessopts=(caslib=casuser timeout=1800 locale="en_US"); caslib _all_ assign; cas mySession sessopts=(caslib="casuser"); ... View more

Good article, thank you. Can you help me with the following problem I face trying to deploy a flow as a job?   https://communities.sas.com/t5/SAS-Viya/issue-with-sas-studio-flow-execution/m-p/956738/highlight/false#M2726      ... View more

Did you set the permissions on the in-memory table or the source file within the caslib? The best practice is to set table-level controls on persisted data (data that has been saved as a source file within a caslib), not on in-memory data. This topic discusses persistence of CAS access controls.  https://go.documentation.sas.com/doc/en/sasadmincdc/v_060/calauthzcas/n1bf0cwn6ae85gn1b64x2j0czu24.htm#n0x4ifvvufllarn151wfj32erz4q ... View more

Here is some more detail about the solution that @acordes suggested:   As far as I can tell, this workaround will only work well if there is one row for each date in the data query. The user experience becomes very confusing if, for example, the row for 27JAN2025 contains the aggregation of 10 values in the underlying data query. (Because the calculation only compares the first and last row in the query, which would not match what is displayed in the list table in this case.)   You will need to create a filter action from the first list table to the one that displays the difference row.   If the user selects multiple rows, it will calculate the difference between the first and last row only. (As the user would probably expect) ... View more

There is no need for TRIM() if you are using CATS() function.  That already removes the trailing spaces from the values. It also removes the leading spaces. data _null_ ; set merged; /* (obs=3 firstobs=3); */ out=&output; path=&path; call execute(cats( '%nrstr(%readReportContent)' ,'(url=',url ,',name=',name ,',path=',path ,',endpoint=',href ,',output=',out ,')' )); run; ... View more

Word does not automatically display the TOC. 1. Generate your word document. 2. press ctrl+a to select all (i.e., the entire document) 3. press f9   https://support.sas.com/resources/papers/proceedings20/4265-2020.pdf Note that Word doesn't automatically display the TOC when you open the document. You can manually display the TOC by pressing CTRL+A F9 on your keyboard. Another Word tip: If you jump f rom the TOC to the body of the report, then you can jump back to the TOC by pressing ALT ←.     ... View more

thanks a lot, I had defined the wrong context, cas management service compute context instead of sas job execution compute context 🙂 ... View more