If you wanted to do this in SAS you could use the macrocore library as follows:   /* get all users */ %mv_getusers(outds=users) /* get all groups */ %mv_getgroups(outds=groups) /* get users in a group */ %mv_getgroupmembers(GROUPNAME,outds=users) /* get groups for a user */ %mv_getusergroups(USERNAME,outds=groups) A guide to setting up the access token is available here.     Note - this only includes the users & groups that have been explicitly added to viya, ie - it's not necessarily the full list of users who can access the box.   ... View more

It's possible, you could create a stored process or even upload your excel to a web application and run this macro:   %mm_createfolder(path=/some/meta/folder)   We use it in our automated builds for Data Controller.  The Viya version of the macro is here. ... View more

I added a macro to the macrocore library that performs this very function.    To execute:   /* compile macro */ filename mc url "https://raw.githubusercontent.com/macropeople/macrocore/master/meta/mm_tree.sas"; %inc mc; /* execute */ %mm_tree(root=/my/path, outds=iwantthisdataset) ... View more

Welcome to the world of building web apps on SAS - probably the best way to use SAS (imho)!   I reproduced your code as a stored process using the MacroCore library here:  https://gist.github.com/allanbowe/4e2bb87250450381389e74f8e45a3a02.js   I then opened Developer tools (F11) and saw the following errors:   After a trying a few things, I realised you were hit with probably one of the hardest-to-detect errors in SAS.   The line length limit!   Your program editor has a limit to the number of characters in a line of code.  Anything longer than approx 1000, and your code is just truncated, without a message.   I split your code into several put statements and it worked:       The final code is here:  https://gist.github.com/allanbowe/1dbb3cc64e430d2f385bb26d27773019   For the future, you will find it much easier to build web apps on SAS using the Web Server.  Simply put your html / css/ js files in the static content folder, and call SAS using an adapter (such as SASjs).  An example (minimal) seed app for doing this is provided here:  https://github.com/macropeople/minimal-seed-app   A full React example is here:  https://github.com/macropeople/react-seed-app   And here's a video of putting it together in 5 mins:  https://www.youtube.com/watch?v=vSNBea_M8yU   An end to end guide for building web apps on SAS is available here:  https://sasjs.io   Now, in case you are saying - "I don't have access to the SAS Web Server and my admin will never leave his cave to even respond to that request" - there is another solution, that doesn't involve hours of copy pasting put statements and apostrophes.   That is - sasjs-cli   This is a client tool that handles the compilation of SAS (backend) data services, and also FRONTEND files such as HTML / CSS / Javascript.  It will wrap your frontend files in put statements, and automatically 'split' them to prevent lines over 120 characters.  You can work locally in your favourite editor, with all your SAS / frontend files tidily arranged in your GIT repo, and simply build / deploy when ready.  The pre-requisite - NodeJS (version 12+).   The workflow:   # install the tool globally (one time) npm install -g sasjs-cli # create a new project sasjs create myapp cd myapp # all your SAS files are under sas/services/(subfolder) # your frontend goes in a folder in the root # update sas/config.json to set streamweb:true and websourcepath:yourwebfolder sasjs build that's it - you now have a deploy script under the `sasbuild` folder that will stream your frontend, and connect it to your backend services.   Enjoy. ... View more

Thanks for calling out the macrocore library!  We recently switched to automatic semantic versioning with every release, so you can be sure of the version you are linking to.    The macros are geared towards application developers, with tools for creating folders, web services (SAS 9 STPs or Viya JES), libraries, you name it. They are tested heavily in our commercial tool (Data Controller) and a part of the SASjs framework.  The documentation is created using DoxyGen and hosted here:  https://core.sasjs.io.   To make the macrocore library even easier to consume we even made a CLI tool for it.  This is brand new and yet to be documented, but the steps are this (note - you will need to install NPM and GIT as described here).   # install the tool globally to add sasjs to your PATH npm i -g sasjs-cli # create a new project for your app sasjs create myFantasticApp cd myFantasticApp # a sample folder structure with sample files is now available # your final programs go inside the services folder # your macros go in the macros folder # the header of each SAS file contains the list of dependencies # dependencies are sourced first from the macros folder then macrocore # the next step will compile your services # this means you will have a SINGLE FILE PER SERVICE with all dependent macros # it will also create a deployment script to register them as web services sasjs build The great thing about this approach is that there is no dependency on the filesystem (as all your dependencies are in the actual service) and the build process will even strip out the comments to reduce filesize.  By forcing dependencies to be in the header you are also ensuring the accuracy of the automated documentation.   It's all fully MIT open source and free to use.   Join my talk at virtual SASGF to learn more! ... View more

I tried it again today, and it worked.  Must have been a critter in a circuitboard somewhere 🙂 ... View more

ha ha - ok.  From what I can tell, it is not possible to do what I am trying to do.  But I admire the approach you took to avoid nesting the regex calls 🙂   accepted. ... View more

done ... View more