dc
0fa5da8abf
mpe_accesscheck and validatefilter validated their libds input with mp_validatecol(LIBDS), which rejects the LIBREF.CATALOGNAME-FC form that Data Controller uses to address a format catalog. A format-catalog load or filter therefore aborted with "Invalid base_table" / "Invalid filter_table" - stagedata, getdata and postdata all reach mpe_accesscheck through the edit/approve path. Add mpe_validatecol, a wrapper that permits the catalog form: the -FC suffix is matched exactly and the remainder is validated as a strict LIBREF.DATASET, so the whole value is covered and a caller that needs the catalog reference downstream (MPE_SECURITY stores it with the suffix) still receives it. getrawdata and getcolvals had grown an inline version of this check that scanned on the dash and validated only the prefix, leaving whatever followed it unvalidated; the wrapper replaces both. mpe_validatecol.test.sas asserts the matrix - plain libds, catalog form, and payloads that smuggle content past a valid libds prefix.
Data Controller for SAS
Control your manual data modifications!
Alternatives to Data Controller include:
- 💾 Developing / testing / deploying / scheduling overnight batch jobs to load files from shared drives
- 🔒 Opening (and locking) datasets in Enterprise Guide or SAS® Table Viewer to perform direct updates
- ❓ Asking a #DBA to run validated code after a change management process
- 🌐 Building & maintaining your own custom web application
- 🏃 Running #SAS or #SQL updates in production
Problems with the above include:
- Legacy 'black box' solutions with little to no testing, documentation or support
- End users requiring direct write access to critical data sources in production
- Upload routines that must be manually modified when the data model changes
- Breaches due to unnecessary parties having access to the data
- Inability to trace who made a change, when, and why
- Reliance on key individuals to perform updates
- Building bespoke ETL for every new data source
- High risk of manual error / data corruption
Data Controller for SAS® solves all these issues in a simple-to-install, user-friendly, secure, documented, battle-tested web application. Available on Viya, SAS 9 EBI, and SASjs Server.
An individual Viya deploy can be done in just 2 lines of #SAS code!
filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/viya.sas";
%inc dc;
For a multi-user deploy, using a shared system account, please see deploy docs.
For further information:
- Main site: https://datacontroller.io
- Docs: https://docs.datacontroller.io
- Code: https://code.datacontroller.io
For support, contact support@4gl.io or reach out on Matrix!
Development
Lighthouse CI
This project includes automated Lighthouse performance and accessibility checks that run on pull requests. The checks ensure:
- Accessibility Score: Minimum 1.0 (100%) median score across all tested pages
The Lighthouse CI workflow:
- Sets up the development environment with SASjs server and mocked services
- Builds and serves the Angular frontend
- Installs Chrome and runs
lhci autorun(Lighthouse CI) against key pages - Uploads results as artifacts for review
To run Lighthouse checks locally:
cd client
npm install
npm run lighthouse
Configuration is in client/lighthouserc.js (URL list, desktop preset, Chrome flags, assertions).