@Vimal08 - we were unable to replicate that issue, however we have decided to just deprecate that function entirely (it was a check on install to ensure the user has the correct version of Node, ie LTS). We've now updated the utils, adapter and CLI repos.  Can you install the latest version (3.19.5 +) and try again? ... View more

We've never deployed or recommended BIWS so I can't answer your question, however I can let you know about an alternative option that may / may not be helpful in your situation (if neither regular Stored Processes nor Viya are amenable options):   https://server.sasjs.io   This is an MIT open source REST API, with session manager, over Foundation SAS.  Works perfectly with Postman and any other client you can think of.  And if there's something missing, you can of course fork the project and add any features yourself.   Disclosure - it's a product built by my team.   ... View more

You could try playing with the headers to do a 302 redirect but I'm not sure if it will work   The "proper" way of handling this would be to have a frontend that: 1.  requests the zip download 2.  redirects to the desired page   This is how we manage it using Data Controller for SAS.     ... View more

I would definitely advise against this approach in production, as it will require very careful management when it comes to promotions / merging etc.  Cloning the repo to your target machine, and pulling as necessary, is far preferable.  Or, building your SAS jobs & services from the target branch, taking GIT out of the picture completely.   But anyways - beyond the approach that @Quentin references, you can also use the `sasjs run` command to execute code from a GIT repo (with the caveat that it will only work where authentication is not required).   Docs: https://cli.sasjs.io/run/#using-github-urls ... View more

One option is to avoid passwords entirely!   We've built a tool that allows end users to make _controlled_ changes using a system account.  It's zero code, and free for 5 users.   Just make the file read-only to everyone, then configure the system account (eg `sassrv`) as the only account with write access.  In this way, all changes are handled with the tool, along with an audit history of all the changes, plus the ability to implement validation checks.   https://datacontroller.io ... View more

It's not exactly what you are asking for, but my team have released a free (for 5 users) browser based tool that has some quite advanced capabilities for viewing SAS datasets. https://datacontroller.io   It can be deployed onto a desktop, just send a PM if you need help with the setup. ... View more

If you don't have EG, or local Base SAS, or the EBI stack, or Viya - there is another option   My team have built a free, open source server for SAS:  https://github.com/sasjs/server   You can install it on your Linux server in 2 lines of code:   curl -L https://github.com/sasjs/server/releases/latest/download/linux.zip > linux.zip unzip linux.zip You can then just run `./api-linux` to launch.  Give it the path to your executable and you immediately have a web server (on port 5000) with SAS in it. If you'd like to do further setup (whitelisting, user accounts, alternative runtimes, permissions etc) check out the docs:  https://server.sasjs.io     ... View more

If I were you I wouldn't care too much about how or where Viya stores your SAS programs.  If your source code is in GIT, you can clone it and manage your files using any IDE on any operating system.  SAS Studio is one option, using git functions, or - for a more realistic 'developer experience' - VS Codium.   You don't have to look very far outside SAS to see that this is the dominant paradigm for code management in most languages.  Clone a repo, make a branch, lint & deploy & test changes, make a pull request, and after it is merged, the new version is deployed. Viya should not be considered more than a simple 'runtime' environment, IMO, and defnitely not the 'source of truth' when it comes to your SAS programs.  That should always be the main branch of your GIT repository.   There are many tools for handling SAS code outside of a SAS runtime, with the benefit that it you can choose your SAS flavour - be that Viya, SAS 9 EBI, or Base SAS. ... View more

To get a list of Viya users:  https://core.sasjs.io/mv__getusers_8sas.html   Viya groups:  https://core.sasjs.io/mv__getgroups_8sas.html   Group Members:  https://core.sasjs.io/mv__getgroupmembers_8sas.html   Member Groups: https://core.sasjs.io/mv__getusergroups_8sas.html   ... View more

Here's a core macro, not as detailed as Greg's but it will probably run a lot faster in a large estate:  https://core.sasjs.io/mm__getlibs_8sas.html ... View more

This macro will convert a dataset to a cards program:  https://core.sasjs.io/mp__ds2cards_8sas.html ... View more

I appreciate it doesn't directly answer your question, but I figured I'd point you to various tools we have built that may help on your journey:   * Folder Navigator. This web app lets you modify STPs in the browser:  https://github.com/sasjs/folder-navigator * Data Controller.  Includes a metadata object explorer you can use to troubleshoot:  https://4gl.uk/dcdeploy * SASjs CLI.  Create Stored Processes from Command Line.  https://cli.sasjs.io * mm_createstp.  A macro to create Stored Processes programmatically.  https://core.sasjs.io/mm__createstp_8sas.html ... View more

We built an alternative to FSEDIT, and it _should_ work on SAS v8, although it hasn't been tested that far back!  Am sure it could though with a few tweaks.   It uses SASjs Server as the middleware, and connects directly to your SAS executable.  Free for 5 users.  Download instructions are here:  https://4gl.uk/dcdeploy ... View more

We built a tool very similar to FSEDIT but with a lot more control and automated validation of the inputs.   It's free for 5 users and works on Viya, SAS EBI, and Base SAS.   You can download / install it from here: https://4gl.uk/dcdeploy     ... View more

that's right, it's not really feasible to build JSON reports in an IDE! We're looking to add VA export / import to the SASjs CLI (https://github.com/sasjs/cli) but it's not ready yet. ... View more