dc/docs.datacontroller.io
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: links
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m42s
Details

Browse Source
This commit is contained in:
zmaj 2024-01-24 11:16:43 +00:00
parent 09d302c309
commit a8580b87f7
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/dcc-tables.md
View File

@ -185,7 +185,7 @@ Leave blank unless using retained / surrogate keys.
### AUDIT_LIBDS ### AUDIT_LIBDS
If this field is blank (ie empty, missing), **every** change is captured in the [MPE_AUDIT](/tables/mpe_audit.md). This can result in large data volumes for frequently changing tables. If this field is blank (ie empty, missing), **every** change is captured in the [MPE_AUDIT](/tables/mpe_audit). This can result in large data volumes for frequently changing tables.
Alternative options are: Alternative options are:

8
docs/excel.md
View File

@ -82,16 +82,16 @@ Through the use of "Excel Maps" you can dynamically extract individual cells or
Configuration is made in the following tables: Configuration is made in the following tables:
1. [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules.md) - detailed extraction rules for a particular map 1. [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules) - detailed extraction rules for a particular map
2. [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md) - optional map-level attributes 2. [MPE_XLMAP_INFO](/tables/mpe_xlmap_info) - optional map-level attributes
Each [rule](/tables/mpe_xlmap_rules.md) will extract either a single cell or a rectangular range from the source workbook. The target will be [MPE_XLMAP_DATA](/tables/mpe_xlmap_data.md), or whichever table is configured in [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md). Each [rule](/tables/mpe_xlmap_rules) will extract either a single cell or a rectangular range from the source workbook. The target will be [MPE_XLMAP_DATA](/tables/mpe_xlmap_data), or whichever table is configured in [MPE_XLMAP_INFO](/tables/mpe_xlmap_info).
To illustrate with an example - consider the following excel. The yellow cells need to be imported. To illustrate with an example - consider the following excel. The yellow cells need to be imported.
![](img/xlmap_example.png) ![](img/xlmap_example.png)
The [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules.md) configuration entries _might_ (as there are multiple ways) be as follows: The [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules) configuration entries _might_ (as there are multiple ways) be as follows:
|XLMAP_ID|XLMAP_RANGE_ID|XLMAP_SHEET|XLMAP_START|XLMAP_FINISH| |XLMAP_ID|XLMAP_RANGE_ID|XLMAP_SHEET|XLMAP_START|XLMAP_FINISH|
|---|---|---|---|---| |---|---|---|---|---|

2
docs/roadmap.md
View File

@ -66,7 +66,7 @@ Format Catalogs can now be viewed, filtered, exported and edited. See [docs](/f
### Change Tracking Information in a Single Transaction Table ### Change Tracking Information in a Single Transaction Table
Now available in [mpe_audit](/mpe_audit.md) Now available in [mpe_audit](/tables/mpe_audit)
### Dynamic Filtering ### Dynamic Filtering

6
docs/tables/mpe_xlmap_data.md
View File

@ -14,9 +14,9 @@ The MPE_XLMAP_DATA table stores the data from complex excel uploads in a vertica
See also: See also:
* [Excel Uploads](/excel.md) * [Excel Uploads](/excel)
* [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md) * [MPE_XLMAP_INFO](/tables/mpe_xlmap_info)
* [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules.md) * [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules)
!!!note !!!note
This table cannot be edited directly! Any target tables configured in [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md) are also removed from the Tables list in the LOAD menu. This table cannot be edited directly! Any target tables configured in [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md) are also removed from the Tables list in the LOAD menu.