Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISSUE: connectionName parameter does not works! #247

Open
ytpl65 opened this issue Oct 26, 2023 · 0 comments
Open

ISSUE: connectionName parameter does not works! #247

ytpl65 opened this issue Oct 26, 2023 · 0 comments

Comments

@ytpl65
Copy link

ytpl65 commented Oct 26, 2023

knowage server: 8.1
ubuntu os: 22.04
BIRT-report-designer: 4.13.0

  1. Datasource Connection:
    image
  2. Dataset Preview
    image
  3. Report Parameters
    image
  4. connectionName parameter:
    image
  5. Parameter Binding
    image
  6. Birt Report Execution:
    image
  7. Data Source configured at knowage server:
    image
  8. Deployed at Knowage server:
    image
  9. Analytical Driver:
    image
  10. Report Executed at knowage server
    image

Now, Compare the data of screenshots of No.6 and No. 10. it is same!
The Knowage server is not using the correct data source when running reports. Even though a connection name parameter is passed when executing the report on the server, it is not pulling data from that data source.

Instead, it is always using the data source defined in the original BIRT report design, regardless of the connection name passed.

The behavior should be:

When a report runs on Knowage server and a connection name parameter is provided, it should fetch and display data from that specified data source.

But it is not working that way. It always defaults back to using the data source hardcoded in the BIRT report design, rather than using the one provided in the connection name parameter as it's supposed to.

So in short, the server is not respecting the connection name parameter and using the wrong data source when reports are executed.

Help Me
Thank You

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant