As there is no workflow or similar in place, it would be great to have identical coloumn names in the reports as well as in the default mapping. That would enable customers to create a data storage based on a report without amending a mapping configuration in JSON.
Hi Freddy,
thx for you idea.
The situation here is a little bit more difficult :)
We have to differentiate between technical column names (e.g. JSON) and reporting column names. In the past we received couple of complaints from customers the technical name thouroufare in our model and report is not understandable.
Additionally, report columns might contain:
Derived information (not directly stored in DB)
Custome calculations
I am happy to review concrete proposals. But for time being we dont plan to change here anything.
Marek