You can get this functionality by using POST EDIT HOOKS in Data Controller for SAS (disclaimer - we built the tool).   It will soon be available natively once we finish the Column Level Security feature:  https://docs.datacontroller.io/column-level-security/   It's free for 5 users and I'd be happy to help you set it up.   https://datacontroller.io ... View more

Great question!   The solution we use - Doxygen and SASjs.   Doxygen is a third party utility that can generate HTML websites from program headers - like this one:  https://core.sasjs.io   We made the process simpler in the SASjs CLI by pregenerating the Doxyfile (config).  The docs for the sasjs command are here:  https://cli.sasjs.io/doc/   As you can see, it even includes a capability to generate data lineage using the program headers. You can even generate your own diagrams using DOT language - see this page (all generated from plain text):  https://core.sasjs.io/mp__stackdiffs_8sas.html ... View more

SAS AMO is a SAS 9 product   You could set up a Stored Process to call Viya if you're running both.  Or, use VBA to call the SAS Viya REST APIs.     Otherwise, you'll have to wait for the office support in Viya (might be out already) that brings connectivity to Office 365.  Not sure about legacy excel though. ... View more

Hi @jins - you were close!  Here are the things I changed to make your code work:    Changed the name to _webout.pdf - this is necessary for the result to stream Added the contentdisp attribute - this is necessary for the file to auto-download Removed the _odsstyle variable (not available in my 3.5 environment) And here is a functional program you can run in SAS Studio to reproduce (just open the link in the log at the end): /* compile sasjs core macros */ filename mc url "https://raw.githubusercontent.com/sasjs/core/main/all.sas"; %inc mc; /* set up the sas program */ filename ft15f001 temp lrecl=1000; parmcards4; filename f_pdf filesrvc parenturi="&SYS_JES_JOB_URI" name='_webout.pdf' contenttype='application/pdf' contentdisp="attachment; filename=my.pdf"; ods pdf file=f_pdf /*style=&_ODSSTYLE */; proc print data=sashelp.class; run; ods pdf close; ;;;; /* create the job in SAS Drive */ %mx_createwebservice(path=/Public/app/demo,name=sendpdf) For reference there are a bunch of examples for streaming files from Viya (or SAS 9, or SASjs server) in this macro:  https://core.sasjs.io/mp__streamfile_8sas_source.html   There's no PDF option yet, but feel free to raise an issue or PR! ... View more

Hi @pmbrown ,   We (4GL Apps) completely agree - you shouldn't be pushing SAS code to GIT without basic lint checks (and testing)!   Which is why we built an MIT open source linter for SAS:  https://github.com/sasjs/lint   As you point out, a linter is a fantastic tool to run as part of a git pre-commit hook, or during a CI/CID pipeline.   You can find it bundled already in the following SASjs tools:   Command Line Interface - https://cli.sasjs.io/lint VS Code Extension - https://github.com/sasjs/vscode-extension Being MIT licensed, you can fork and include it within any tool you wish, no restrictions whatsoever.   We're looking for partners and sponsors and contributors to improve the tool.  Just contact me here (PM) or on the website:  https://sasapps.io/contact   The full list of rules can be found in this JSON file:  https://github.com/sasjs/lint#linting   And a video here:  https://communities.sas.com/t5/SAS-Hacker-s-Hub/Hacker-tip-5-Linting-SAS-Code/td-p/801098   Anyone is free to contribute rules - we wrote a contributors guide here:  https://github.com/sasjs/lint/blob/main/CONTRIBUTING.md   By the way - you can also fix a lot of issues (such as your example of avoiding basic REPLACEing of datasets) by simply running SAS in strict mode - see this macro (which runs at the start of ALL the apps my team produce):  https://core.sasjs.io/mp__init_8sas.html ... View more