I am not sure how we want to solve this problem. The situation is, that we define a process part and do not reset it when changing the view (in the same way that we do not change the configuration when changing the view). The backend however returns 500 for this request because having a process part does not make sense for this view.
We have two ways to deal with this:
- We try to determine when to reset the process part when updating the report in the frontend. That would be inconsistent with how we do it for the visualization configuration, where we keep the fields even if they do not make sense for the current visualization
- We ignore the process part when evaluating the report, which would maybe make the API harder to understand (I can define a process part but sometimes it is ignored and other times not)
Johannes Heinemann, Sebastian Bathke, any thoughts?