• v7.21.0 Stable

    gitea-actions released this 2026-10-29 16:32:53 +00:00 | 271 commits to main since this release

    Data Controller for SAS - v7.21.0

    Released 29 October 2026.

    This release closes a gap in the Visual Analytics embed that only shows up with particular report prompts: a date parameter whose display format is not DATE9 reaches Data Controller as text (January 1, 2026), could not be converted, and was dropped - so the report looked connected while that one prompt filtered nothing. Written dates are now parsed to a SAS date literal like any other date prompt.

    Two smaller changes ride along: the derived-variable hook now runs the core field scan over the expression it is handed, and the demo seed names the server group it seeds into instead of relying on the caller's default.

    There is no security content in this release, and no migration or configuration change - nothing to run after deploying. An existing report object behaves exactly as it did, except that a written-format date prompt which previously did nothing now filters.

    For installation / upgrade instructions, visit https://docs.datacontroller.io/


    Highlights

    Written dates from a report prompt

    VA sends the prompt's display value, not a raw SAS number, and the display format is whatever the report author chose. DATE9 (12FEB1960) was already understood; a prompt formatted differently arrives as January 1, 2026 and used to be discarded, because the value did not look like a date.

    The parser now accepts a month name spelled out or abbreviated, day before or after the month, with a comma, a dot or a dash between them:

    Value the report sends Clause Data Controller builds
    12FEB1960 '12FEB1960'd
    January 1, 2026 '01JAN2026'd
    Jan 1, 2026 '01JAN2026'd
    Jan. 1, 2026 '01JAN2026'd
    1 January 2026 '01JAN2026'd
    1-Jan-2026 '01JAN2026'd

    A month with no day (January 2026) is not a date and is still rejected rather than being read as the first of the month - a wrong filter is worse than no filter. The applied clause appears above the grid as usual, so what the parameter did is visible without opening the editor.

    Derived variables are checked by the core field scan

    The MPE_DERIVED hook applies the core field scan to the derived expression, so a derived variable is checked with the same rules as a stored column before the submission is staged.

    Demo data that a date filter can actually exercise

    The demo table seeded a date per row rather than dates that repeat, so filtering it by date returned one or two rows and made a working filter look broken. The seed now cycles 24 first-of-month dates across two years, and the estate seed names the sasjs server group explicitly rather than inheriting the caller's.

    If you are upgrading

    Nothing to run and nothing to configure. Deploy as usual.

    • A report object with a DATE9 date prompt is unaffected.
    • A report object whose date prompt uses a written format starts filtering where it used to be silently ignored - check those reports after upgrading, because a filter that did nothing may now return fewer rows than expected. That is the fix working, not a regression.

    Known issues

    • dc/dc#404: a va_parmap entry naming a column the table does not have shows the mapping banner as intended, but the first validation request still aborts behind it, so the report author sees an abort modal as well as the banner. Diagnosed and documented; not fixed in this release.

    Verifying the download

    Every asset on this release is covered by the SHA256SUMS file. To verify a download, fetch SHA256SUMS from the release assets alongside the files you downloaded, then run:

    sha256sum --check SHA256SUMS --ignore-missing
    

    The command reports OK for each asset that matches. --ignore-missing lets you check just the files you downloaded rather than all of them.

    What this protects: a matching checksum confirms the asset is byte-for-byte the file this pipeline uploaded, guarding against corrupted or tampered downloads (mirrors, proxies, interrupted transfers). It is not a signature: the hashes travel in the same release as the files, so a compromise of the forge itself could alter both. Treat it as an integrity check, not a trust anchor.

    Full changelog

    https://git.datacontroller.io/dc/dc/compare/v7.20.0...v7.21.0

    For installation instructions, please visit https://docs.datacontroller.io/

    Downloads