Details

    • Type: New Feature
    • Status: Closed
    • Severity: Unknown
    • Resolution: Fixed
    • Affects Version/s: 3.8.0 (3.8.0 GA Platform Release)
    • Component/s: None
    • Labels:
      None
    • 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

      Summary of problem:
      These reports have been developed using custom JDBC data source.
      When running the report for the first time report runs smoothly. But, when the report is run the second time round, selection of first run is left behind in the cascaded prompt list until we make a correct selection. Report runs fine when we make the right selections. In case of a prompt which is supposed to display VALUE and use ID for other query then, in the second run the ID is left behind.

      If a dependent prompt becomes invalid, it shouldn't have ANY selection. What it currently does, is show the KEY VALUE (which was not visible prior and should never be presented to a user) of the invalidated selection.

        Issue Links

          Activity

          Hide
          kcruzada Kurtis Cruzada added a comment -

          Have you tried using the setting org.pentaho.reporting.engine.classic.core.ParameterAutoFillsSelection to TRUE in configuration properties?

          This defines whether list-parameter without a value default to the first value in the list of available values. This property defaults to false.

          Show
          kcruzada Kurtis Cruzada added a comment - Have you tried using the setting org.pentaho.reporting.engine.classic.core.ParameterAutoFillsSelection to TRUE in configuration properties? This defines whether list-parameter without a value default to the first value in the list of available values. This property defaults to false.
          Hide
          jagdeesh.ss Jagdeesh.SS (Inactive) added a comment -

          Hi Kurtis,

          I checked it as mentioned by you in the linked ESR, it is not working.

          Thanks,
          Jagdeesh

          Show
          jagdeesh.ss Jagdeesh.SS (Inactive) added a comment - Hi Kurtis, I checked it as mentioned by you in the linked ESR, it is not working. Thanks, Jagdeesh
          Hide
          tmorgner Thomas Morgner added a comment -

          The parameter is probably not set to validate the values. Is the strict-values flag set to true?

          If it is false, the engine accepts any value as valid. If we then have no matching record in the list of available values, we cannot throw that value away as the user said all values are acceptable and acceptable input must never be discarded.

          Cant see a bug here. Smells like invalid parameter definition to me.

          Show
          tmorgner Thomas Morgner added a comment - The parameter is probably not set to validate the values. Is the strict-values flag set to true? If it is false, the engine accepts any value as valid. If we then have no matching record in the list of available values, we cannot throw that value away as the user said all values are acceptable and acceptable input must never be discarded. Cant see a bug here. Smells like invalid parameter definition to me.
          Hide
          tmorgner Thomas Morgner added a comment -

          This case actually might be resolved via the PRD-3451 fix.

          Show
          tmorgner Thomas Morgner added a comment - This case actually might be resolved via the PRD-3451 fix.
          Hide
          anthonycarter Anthony Carter added a comment -
          Show
          anthonycarter Anthony Carter added a comment - See PRD-3451

            People

            • Assignee:
              kcruzada Kurtis Cruzada
              Reporter:
              jagdeesh.ss Jagdeesh.SS (Inactive)
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: