docs(derived): publish the page, and the images for the computed-column styling
The screenshots were taken on the mocked estate, before setvars began marking computed columns with an fx badge, a tinted header and a left edge where the derived block starts. They are re-taken against a real SAS backend, so the images show what ships, and the page describes the marking. The draft banner comes off both pages, the (draft) suffix off both nav entries, and the roadmap gains its Delivered Features entry - all held until the release lands.
No files matched your search
@@ -6,11 +6,6 @@ description: Derived variables are computed columns that appear in the EDIT scre
|
||||
|
||||
# Derived Variables
|
||||
|
||||
!!! warning "Draft - not in a release yet"
|
||||
This page describes a feature that is in development. It is published early so
|
||||
the wording and the screenshots can be reviewed; the behaviour described here
|
||||
ships in the next release.
|
||||
|
||||
A derived variable is a column that does not exist in the target table, but is computed when the table is loaded into the [EDIT screen](/dc-userguide/#editor). It is read-only, it appears after the physical columns, and it can be filtered on like any other column.
|
||||
|
||||
Derived variables are useful when users need to work with a value that is a function of the stored data - a banding, a concatenation, a calculation - without changing the table, the load process, or the ETL.
|
||||
@@ -23,6 +18,8 @@ The table below is shown in the EDIT screen. `LINE_VALUE` is `QTY * PRICE` and `
|
||||
|
||||

|
||||
|
||||
The computed columns are marked apart from the physical ones: a tinted header with an `fx` badge, tinted italic cells, and a left edge where the derived block begins. They are read-only, and the marking says so - a column that is locked by a rule or by column level security is dimmed instead, which is a different message from "computed here". Hovering a header shows the variable's label, or its name and expression where no label was configured.
|
||||
|
||||
Because the derived columns are created before the filter is applied, they can be filtered like any other column. Here `REGION = 'West'` selects the two western states, and the filter bar names the derived variable:
|
||||
|
||||

|
||||
|
||||
|
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 141 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 57 KiB |
|
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 52 KiB |
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 61 KiB |
@@ -178,3 +178,7 @@ Delivered in v7.13.0. Formula columns (HARDFORMULA / SOFTFORMULA) are computed
|
||||
### Regex Rules
|
||||
|
||||
Delivered. HARDREGEX (blocking) and SOFTREGEX (warning) rules validate cell values against a Perl-style regular expression. See [Regex Rules](/dcc-validations/#regex-rules).
|
||||
|
||||
### Derived Variables
|
||||
|
||||
Computed columns can be configured per table, so the EDIT screen shows values that are not stored anywhere - a banding from a code, a multiplication of two columns - and they can be filtered on like any other column. The configuration lives in [MPE_DERIVED](/tables/mpe_derived/), and the grid marks the computed columns with an `fx` badge. See [docs](/derived-variables)
|
||||
@@ -6,11 +6,6 @@ description: The MPE_DERIVED table is used to configure computed columns that ap
|
||||
|
||||
# MPE_DERIVED
|
||||
|
||||
!!! warning "Draft - not in a release yet"
|
||||
This page describes a feature that is in development. It is published early so
|
||||
the wording and the screenshots can be reviewed; the behaviour described here
|
||||
ships in the next release.
|
||||
|
||||
The MPE_DERIVED table is used to configure derived (computed) variables - columns that are created when a table is loaded into the EDIT screen, so that they can be displayed and filtered on without being stored. More details are available in the [user guide](/derived-variables/)
|
||||
|
||||
The table is itself registered in [MPE_TABLES](/tables/mpe_tables/), so it is maintained through the EDIT screen with the usual review and approve workflow.
|
||||
|
||||
@@ -33,7 +33,7 @@ nav:
|
||||
- MPE_DATASTATUS_TABS: tables/mpe_datastatus_tabs.md
|
||||
- MPE_DATADICTIONARY: tables/mpe_datadictionary.md
|
||||
- MPE_DATALOADS: tables/mpe_dataloads.md
|
||||
- MPE_DERIVED (draft): tables/mpe_derived.md
|
||||
- MPE_DERIVED: tables/mpe_derived.md
|
||||
- MPE_EMAILS: tables/mpe_emails.md
|
||||
- MPE_EXCEL_CONFIG: tables/mpe_excel_config.md
|
||||
- MPE_FILTERANYTABLE: tables/mpe_filteranytable.md
|
||||
@@ -60,7 +60,7 @@ nav:
|
||||
- CAS Tables: cas-tables.md
|
||||
- Column Level Security: column-level-security.md
|
||||
- Dates / Datetimes: dcc-dates.md
|
||||
- Derived Variables (draft): derived-variables.md
|
||||
- Derived Variables: derived-variables.md
|
||||
- Dynamic Cell Dropdown: dynamic-cell-dropdown.md
|
||||
- Emails: emails.md
|
||||
- Excel: excel.md
|
||||
|
||||