excel updates
This commit is contained in:
1 parent
d074aee048
commit
198d11a9f2
5 files changed
+29
-10
No files matched your search
+23
-4
@@ -1,9 +1,11 @@
|
||||
# Data Controller for SAS: File Uploads
|
||||
|
||||
Files can be uploaded via the Editor interface - first choose the library and table, then click "Upload". Currently only CSV files are supported, although these can be provided with non standard delimiters (such as semicolon).
|
||||
Files can be uploaded via the Editor interface - first choose the library and table, then click "Upload". All versions of excel are supported. If loading very large files (eg over 10mb) it is more efficient to use CSV format, as this bypasses the local rendering engine, but also the local DQ checks - so be careful! For CSV, alternative delimiters can be used (eg semicolons).
|
||||
|
||||
<img src="/img/dcu-files1.png" height="350" style="border:3px solid black" >
|
||||
|
||||
## CSV Uploads
|
||||
|
||||
The following should be considered when uploading data in this way:
|
||||
|
||||
- A header row (with variable names) is required
|
||||
@@ -20,8 +22,25 @@ The following should be considered when uploading data in this way:
|
||||
- space
|
||||
- underscore
|
||||
|
||||
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.
|
||||
When loading dates, be aware that the data controller makes use of the `ANYDTDTE` and `ANYDTDTTME` informats (width 19).
|
||||
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. Note that UTC dates with offset values (eg `2018-12-26T09:19:25.123+0100`) are not currently supported. If this is a feature you would like to see, contact us.
|
||||
|
||||
!!! 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
|
||||
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
|
||||
|
||||
## Excel Uploads
|
||||
|
||||
Thanks to our pro license of [sheetJS](https://sheetjs.com/), we can support all versions of excel, and extract the data super quickly to boot.
|
||||
|
||||
The rules for data extraction are:
|
||||
|
||||
* Scan the spreadsheet until a row is found with all the target columns (with no blank cells between columns)
|
||||
* Extract data below that row up until the first blank primary key value
|
||||
|
||||
This is incredibly flexible, and means:
|
||||
|
||||
* data can be anywhere, on any worksheet
|
||||
* data can contain additional columns (they are just ignored)
|
||||
* data can be completely surrounded by other data
|
||||
|
||||
A copy of the original Excel file is also uploaded to the staging area. This means that a complete audit trail can be captured, right back to the original source data.
|
||||
Reference in new issue
Block a user