| Category: | Enhancement request |
Priority: | Normal |
Status: | New |
| Project: | Severity: | Minor |
Resolution: | Open |
|
| Component: | Reproducibility: | N/A |
Assigned to: |
For me it's not understandable why predefined input controls have the parameter name bound to the resource id in the repository. This behavior has two big disadvantages for me:
* If you made a mistake in with the parameter name, you have to throw away the complete input control and create a new one from scratch. Especially problematic if the control is already assigned to reports -> you have to alter the report unit, too.
* It's not possible to define multiple controls with the same parameter name and share them in one global folder (e.g. with different queries behind).
If technically possible, I would suggest to add an additional config item to the input control for the parameter name which stays editable and have the resource id (which can be changed only at creation time) separated. (But still use the resource ID to connect the input control to a report unit.)
