fix: links
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m42s
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m42s
This commit is contained in:
parent
09d302c309
commit
a8580b87f7
@ -185,7 +185,7 @@ Leave blank unless using retained / surrogate keys.
|
||||
|
||||
### 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:
|
||||
|
||||
|
@ -82,16 +82,16 @@ Through the use of "Excel Maps" you can dynamically extract individual cells or
|
||||
|
||||
Configuration is made in the following tables:
|
||||
|
||||
1. [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules.md) - detailed extraction rules for a particular map
|
||||
2. [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md) - optional map-level attributes
|
||||
1. [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules) - detailed extraction rules for a particular map
|
||||
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.
|
||||
|
||||
![](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|
|
||||
|---|---|---|---|---|
|
||||
|
@ -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
|
||||
|
||||
Now available in [mpe_audit](/mpe_audit.md)
|
||||
Now available in [mpe_audit](/tables/mpe_audit)
|
||||
|
||||
### Dynamic Filtering
|
||||
|
||||
|
@ -14,9 +14,9 @@ The MPE_XLMAP_DATA table stores the data from complex excel uploads in a vertica
|
||||
|
||||
See also:
|
||||
|
||||
* [Excel Uploads](/excel.md)
|
||||
* [MPE_XLMAP_INFO](/tables/mpe_xlmap_info.md)
|
||||
* [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules.md)
|
||||
* [Excel Uploads](/excel)
|
||||
* [MPE_XLMAP_INFO](/tables/mpe_xlmap_info)
|
||||
* [MPE_XLMAP_RULES](/tables/mpe_xlmap_rules)
|
||||
|
||||
!!!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.
|
||||
|
Loading…
Reference in New Issue
Block a user