-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Context:
There are currently two csv export endpoints in Optimize. The first, "csv/{reportId}/{fileName}", takes a reportID and returns a csv export based on the contents of the TableColumnDto in that reports config (used when exporting a raw data report in the report builder). The second one, "csv/process/rawData/{fileName}" (used e.g. in branch analysis instance ID export) takes a ProcessRawDataCsvExportRequestDto, which has a list of includedColumns, but no excluded. The logic here is that everything that is not in the includedList is to be excluded. This differs slightly from the first endpoint, where for example dto fields are all included unless excluded explicitly and new variables might be automatically included based on the includeNewVariable flat in TableColumnDto.
It is not obvious in the backend why the logic differs between the two endpoints, which can be quite confusing.
This should be resolved, for example by adjusting the ProcessRawDataCsvExportRequestDto to use a TableColumnDto instead of a list of included columns, or alternatively renaming the endpoint so the use case becomes more obvious.
AT:
- the export csv endpoints are adjusted to resolve the above inconsistency/make it easier to understand
- the changes are documented on confluence
- if required, the frontend is adjusted according to the API changes
This is the controller panel for Smart Panels app
- depends on
-
OPT-4031 adjust report configuration to allow specifically including certain columns
-
- Done
-