The feature post: why a computed column is not filterable in a single DATA
step, the view that makes it so, the MPE_DERIVED configuration, dependency
ordering by VAR_DEPS, and what the feature will not do. Three screenshots from
the EDIT screen - the grid, a filter on a character derived column, and a
filter on a numeric one.
The post has moved to the docs site as a Developer Guide page:
https://docs.datacontroller.io/developer-guide/two-rule-sets-one-table/
- content/blog/two-rule-sets-one-table/ is removed (the images moved to the
docs repo, where the page now lives).
- static/two-rule-sets-one-table/index.html keeps the old URL working with a
client-side redirect to the new page, plus a canonical link and noindex.
A static file at that path is served the same way the removed Gatsby page
was (both are index.html under a directory).
mp_lockanytable keys its control table on (lock_lib, lock_ds), and the
approve service takes that lock on the base table named in the submit
record. The MPE_DATALOADS staleness check is keyed the same way. So two
registrations of one physical file neither lock nor observe each other,
and a second approval can overwrite the first silently.
Spell that out, note that the hook route routes both mirrors to one base
table and so does not have the gap, and give the two ways to close it.
The special missings video was labelled "Retain Formulas when Loading Excel
to SAS", which is a different video. Restores the one-line correction that
was in the earlier revision of this branch, kept separate from the feed post.
The /static/* path sits behind a Cloudflare cache-everything rule with a
62-day edge TTL. An image fetched mid-deploy can pin a bad (truncated/404)
response at an edge POP. Re-encoding produces new content-hashed URLs so
every variant is fetched fresh from origin. Pixels are identical.
dc
allan
sead