Uploaded image for project: 'Pentaho Reporting and Pentaho Report Designer'
  1. Pentaho Reporting and Pentaho Report Designer
  2. PRD-3540

Cascading prompts with server side calculated default values are not working

    Details

    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.

      Description

      The server values the input from the URL higher than the calculated values from the parameter subsystem. This causes troubles when the parameter subsystem replaces the user input with new values.

        Activity

        Hide
        tmorgner Thomas Morgner added a comment -

        A demo report showing the effect of this bug. In PRD, a selection of a product line resets the selection of a product to the first entry of the list. In the server, the old user input prevails and therefore the user sees a the raw product code for a product that is not part of the currently selected product line.

        Show
        tmorgner Thomas Morgner added a comment - A demo report showing the effect of this bug. In PRD, a selection of a product line resets the selection of a product to the first entry of the list. In the server, the old user input prevails and therefore the user sees a the raw product code for a product that is not part of the currently selected product line.
        Hide
        tmorgner Thomas Morgner added a comment -

        Fixed. Note that there was a conflict between the cascading prompt and the fix for BI-Server 5538 (always autoselect first element of a combobox), which would cause the attached report to show an error (you need to select a value) when the UI then auto-selects the value for the user.

        Auto-selecting values in case of empty list parameters should be under the control of the server. We have a global config option

        org.pentaho.reporting.engine.classic.core.ParameterAutoFillsSelection=false

        and a per-parameter setting to allow this sort of thing on the server side. This way, the validating methods can jump in and that auto-selected value can be used by the subsequent parameters in queries and for other validation purposes.

        I therefore disabled that particular fix when the parameter-ui communicates with the reporting plugin. When the parameter UI is used for parametrizationg of any other component (analzyer, dashboard, charts, whatever) the fix for BI-Server 5538 is active.

        Show
        tmorgner Thomas Morgner added a comment - Fixed. Note that there was a conflict between the cascading prompt and the fix for BI-Server 5538 (always autoselect first element of a combobox), which would cause the attached report to show an error (you need to select a value) when the UI then auto-selects the value for the user. Auto-selecting values in case of empty list parameters should be under the control of the server. We have a global config option org.pentaho.reporting.engine.classic.core.ParameterAutoFillsSelection=false and a per-parameter setting to allow this sort of thing on the server side. This way, the validating methods can jump in and that auto-selected value can be used by the subsequent parameters in queries and for other validation purposes. I therefore disabled that particular fix when the parameter-ui communicates with the reporting plugin. When the parameter UI is used for parametrizationg of any other component (analzyer, dashboard, charts, whatever) the fix for BI-Server 5538 is active.
        Hide
        kcruzada Kurtis Cruzada added a comment -

        step to validate....
        opened the report in report designer.
        preview the report.
        select a line.
        select a product name.
        switch to another line.
        verify there is a product name. the bug was that the product code displayed.

        publish the report to the server.
        open the report from PUC
        select a line.
        select a product name.
        switch to another line.
        verify there is a product name. the bug was that the product code displayed.

        Show
        kcruzada Kurtis Cruzada added a comment - step to validate.... opened the report in report designer. preview the report. select a line. select a product name. switch to another line. verify there is a product name. the bug was that the product code displayed. publish the report to the server. open the report from PUC select a line. select a product name. switch to another line. verify there is a product name. the bug was that the product code displayed.

          People

          • Assignee:
            kcruzada Kurtis Cruzada
            Reporter:
            tmorgner Thomas Morgner
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: