improved guide for file uploads

This commit is contained in:
Allan Bowe 2018-09-28 14:24:32 +02:00
parent 0c29aa653d
commit 12e3150ce1
2 changed files with 6 additions and 3 deletions

View File

@ -40,7 +40,7 @@ The Editor screen lets users who have been pre-authorised (via the `DATACTRL.MPE
1 - *Filter*. The user can filter before proceeding to perform edits.
2 - *Upload*. The user can upload a CSV file directly, instead of using the interface. The CSV must have the same structure as the target. Use the 'download csv' option in Viewer to obtain a template of this CSV.
2 - *Upload*. If you have a lot of data, you can [upload it directly](dcu-fileupload). The changes are then approved in the usual way.
3 - *Edit*. This is the main interface, data is displayed in tabular format. The first column is always "Delete?", as this allows you to mark rows for deletion. Note that removing a row from display does not mark it for deletion! It simply means that this row is not part of the changeset being submitted.
The next set of columns are the Primary Key, and are shaded grey. If the table has a surrogate / retained key, then it is the Business Key that is shown here (the RK field is calculated / updated at the backend). For SCD2 type tables, the 'validity' fields are not shown. It is assumed that the user is always working with the current version of the data, and the view is filtered as such.

View File

@ -3,12 +3,12 @@
Files can be uploaded via the Editor interface - first choose the library and table, then click "Upload".
<img src="/img/dcu-files1.png" height="350" >
<img src="/img/dcu-files1.png" height="350" style="border:3px solid black" >
The following should be considered when uploading data in this way:
- A header row (with variable names) is required
- Variable names must be the identical to the target (although this is not case sensitive)
- Variable names must match the target
- Duplicate variable names are not permitted
- Missing columns are not permitted
- Additional columns are ignored
@ -17,3 +17,6 @@ The following should be considered when uploading data in this way:
When loading dates, be aware that the data controller makes use of the `ANYDTDTE` and `ANYDTDTTME` informats.
This means that uploaded date / datetime values should be unambiguous (eg `01FEB1942` vs `01/02/42`) to avoid confusion - as the latter could be interpreted as `02JAN2042` depending on your locale and options `YEARCUTOFF` settings.
!!! tip
To get a copy of a file in the right format for upload, use the [file download](/dc-userguide/#usage) feature in the Viewer tab