Closed KonradUdoHannes closed 4 years ago
The column actually is present and gets prefixed with its corresponding statisitic as expected. So the result contains a column BEVSTD_GES
. The actual problem now is, that the column ordering does not work as expected and BEVSTD_GES
is between the source column and therefore not that visible. Column ordering should address this. To address the bug when mapping enum values to the verbose descriptions the functionality should properly identify BEVSTD_GES
and the column to be mapped (instead of trying to map GES as it does right now.)
Description
When creating a query with two or more statistics and an enum column for one of them, the verbose_enums flag of
.results
causes a key error.What I Did