fix: roadmap
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m50s
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m50s
This commit is contained in:
parent
79da26a21d
commit
48ad6e6be9
@ -37,11 +37,6 @@ The following changes are necessary to implement this feature:
|
||||
* Updates to documentation
|
||||
* Release Notes
|
||||
|
||||
### Complex Excel Uploads
|
||||
|
||||
Our customer was ingesting Basel III reports into SAS and needed an easy to use mechanism for extracting very specific cells and ranges from a complex and constantly changing workbook format.
|
||||
|
||||
The changes we made to deliver this feature are described here: https://git.datacontroller.io/dc/dc/issues/69
|
||||
|
||||
### API Submissions
|
||||
|
||||
@ -156,3 +151,13 @@ It was necessary to find a way to restrict the tables which certain groups could
|
||||
**Solution**
|
||||
|
||||
We added a [new access level](/dcc-security/#view) in the MPE_SECURITY table so that access could be restricted at both TABLE and LIBRARY level.
|
||||
|
||||
### Complex Excel Uploads
|
||||
|
||||
Our customer was ingesting Basel III reports into SAS and needed an easy to use mechanism for extracting very specific cells and ranges from a constantly changing workbook format.
|
||||
|
||||
**Solution**
|
||||
|
||||
We built an approach that allowed end users to define a series of rules for importing cells and ranges from anywhere within a workbook - based on absolute / relative positioning, or using search strings.
|
||||
|
||||
The changes we made to deliver this feature are described [here](https://git.datacontroller.io/dc/dc/issues/69) and the final documentation is [here](/excel).
|
Loading…
Reference in New Issue
Block a user