You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
knowage server: 8.1
ubuntu os: 22.04
BIRT-report-designer: 4.13.0
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
The text was updated successfully, but these errors were encountered: