nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Integration of HTML/JS into the Report Layout

cdoniat

Hi everyone,

I tried this best practice (point 6 and 7) that it fit with my needs: http://esitnikov.blogspot.com/2010/01/birt-best-practice_5227.html

However, the binding between 'queryParam' and property binding is not described at all.
I asked Evgeny. He is busy actually.

If anyone had already the chance to try this, let me know

Thanks in advance,

Christophe

Find more posts tagged with

Comments

mwilliams

Hi Christophe,

Can you explain more of what you're wanting to know? Are you asking how you use the property binding to set the query based on a parameter like in the example?

johnw

His example is REALLY confusing, so I don't blame you for not following it.

In 6.2, the section about property binding, he is explaining that you can override what you have set for any of the properties of a data set. In the example given, he is actually overriding the full select query. What he has is a report query that has several different options, so picture a Drop Down parameter, with the values of F, B, and E. Depending on the value selected in the report parameter dialog, the Property Binding is going to override the entire select statement.

So for the sake of description, if the user selects F, the select statement would be:
select
F as value
from
table

for B:
select B as value
from table

and for E it would be:
select
E as value
from
different_table_same_structure

The point being that the property binding will totally override the query, so the entire select statement is necessary. This is similar to setting the queryString property in a Data Sets onOpen event. But property binding exists in a lot of report items, not just data sets. For example, you can use it in a Data Source to change a JDBC URL parameter based on the environment being run in, so you wouldn't need multiple Data Sources for a development environment vs a Production Environment. Personally I prefer to use Event Handling in most cases since this provides a visual indication of any advanced scripting in the outline, where Property Binding will not, but Property Binding does open some interesting opportunities.

Point 7 is showing a way of integrating straight HTML into a report design. This can be any HTML, so you can do all sorts of things like manipulate DOM elements in your final report design. Keep in mind that any HTML you insert will be client side only, so it will only change anything in the final output on the users browser. He doesn't elaborate on what he means by "when used with Property Binding" since any HTML javascript is not the same as an expression or event handler in birt, which are both server side javascript. I also do not recommend putting form elements in a final report design. In any cases where you need advanced selectability of elements in a form, use an external form, and if you need data elements from BIRT data, get it through the report engine.

John

cdoniat

Thanks William and John.

It's the point:

"In any cases where you need advanced selectability of elements in a form, use an external form, and if you need data elements from BIRT data, get it through the report engine."

I've got twice choices, either doing with report parameters with default values, but he seems disagree with that or I think I'm putting an external form to make the filters and reload the report

Christophe

mwilliams

"In any cases where you need advanced selectability of elements in a form, use an external form, and if you need data elements from BIRT data, get it through the report engine."

Where do you find this quote in that article? I'm not seeing it.

Can you explain what it is exactly that you're trying to do? Maybe John or I can then just help with your issue specifically rather than breaking down this blog.

cdoniat

Ho I'm sorry William, it is in reply's John not in the Evgeny's blog. Sure I need help but the true is I'm in hurry.

What I'm trying to do? I'd like to get the parameter called queryParam like:

http://localhost:8080/birtViewer/frameset?__report=<reportname>.rptdesign&__format=html&__title=My Report Viewer&__showtitle=false&queryParam='+the_value+';

In this below script that I put in a text control in my report so that I could change filter value and reload my chart with the new value when I submit the form:

<form name=myform>
<select name=choices>
<option name="All" value="All"> All </option>
<option name="AAA" value="AAA"> AAA </option>
<option name="BBB" value="BBB"> BBB </option>
<option name="CCC" value="CCC"> CCC </option>
</select>
<input type="button" onclick="reload_chart(choices.value)" value="Reload Chart">

<script>
function reload_chart(the_value) {

//Build url and call it
var url = 'http://localhost:8080/birtViewer/frameset?__report=Maturity1.rptdesign&__format=html&__title=My Report Viewer&__showtitle=false&queryParam='+the_value+';
window.location = url;
}
</script>
</form>

however, I missed something to get the value of queryParam from the URL and put in a new 'select' statement. I thought get this value in 'beforeOpen' script but I'm not sure about this:

beforeOpen: (I tried this to see the value in the console. Nothing appened).
importPackage(Packages.java.lang);

if (params["versionParam"].value != null) {

System.out.println("VersionParam = " + reportContext.getParameterValue("versionParam"));
System.out.println("VersionParam = " + reportContext.getHttpServletRequest().getParameter("versionParam"));

}

if (params["configParam"].value != null) {

System.out.println("configParam = " + reportContext.getParameterValue("configParam"));
System.out.println("configParam = " + reportContext.getHttpServletRequest().getParameter("configParam"));

}

Any clue?

Regards,

Christophe

mwilliams

Christophe,

So, you've got a report with a chart and you want to reload the report passing a new parameter selected by the user out of your text control form within your report? Pretty much setting up your own drill through? If so, you should be able to have a hidden report parameter named whatever the parameter name is you use in your URL. Then, you can grab the parameter value in your beforeOpen script of your dataSet with params["parameterName"] to build your select statement with the new parameter value you passed through the URL. Maybe I'm not understanding the hangup you're having.

cdoniat

Williams,

Ahh joy! Thanks, first step is the state 'hidden report parameter' I missed in the dialog box of definition of a report parameter, that's the hangup I had. Now in the property binding script I'd like to call the related stored procedure. Is it possible to do a 'call procedurename(param1, param2)'? What is a good syntax?

Regards,

Christophe

mwilliams

Christophe,

If you're writing the stored procedure call in the property binding area, you should be able to do what you did above and call the parameter values with your params["parameterName"].

cdoniat

Williams,

Finally, I found the syntax: "CALL storedprocname('p1','p2')"

so far thanks for your help, you unstucked me.

Regards,

Christophe

cdoniat

Hi William or John,

To call the stored procedure, the syntax is {call procname(arg1,arg2}}.

Another, in the expression builder in property binding, is it possible to call a stored procedure? Because I can't do find the right syntax. I tried the same above and some variants but it doesn't worked.
I looked though the Web without any answer.

Any idea?

Regards, Christophe

mwilliams

Christophe,

Are you receiving and error? The query text is a string. Are you returning the "query" you build as a string?

cdoniat

William,

The following items have errors:

Chart(id = 29):
+ An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: dataset
Cannot set the string value (All) to parameter 1.
org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot set preparedStatement parameter string value.
SQL error #1: Parameter index out of range (1 > number of parameters, which is 0).
;
java.sql.SQLExecption: Parameter index out of range (1 > number of parameters, which is 0).

Which is weird because it is considering that I've got zero parameters?

Christophe

mwilliams

Christophe,

Can you attach your report design so I can see all you've done?

What type of parameter is the parameter that you're trying to assign "All" to?

cdoniat

William,

I attached it.

The type of the parameter is string or varchar(8) in the stored procedure.

Christophe

mwilliams

Christophe,

It looks like there must have been an issue with the upload. Can you try again?

mwilliams

If it doesn't work again, you can just email it to me.

mwilliams@birt-exchange.com

cdoniat

Hi Micheal,

I'm sorry, I was off.

I sent the file by email.

Regards,

Christophe

mwilliams

Christophe,

I see a couple things that could possibly cause an issue in your text control where you build the URL in the config parameter. you put configParam in the URL rather than ConfigParam like the parameter is named and you set the value of the parameter to configParam rather than 'value' like the function states.

cdoniat

Michael,

Thanks for you relevant points. Another try gave me the same error had mentioned before about number of parameter still 0 rather than 2.

Christophe

cdoniat

Hi Michael,

Finally, I backed up with the classical report parameter dialog box at this moment. It's working. But my goal is to put controls (combobox, button) in the report with HTML format and deal with it.

Regards,

Christophe

mwilliams

Christophe,

Can you recreate what you're trying to do with the HTML text control with the sample database so that I can work with it?

cdoniat

Hi Michael,

I'll send you soon,

Thanks anyway,

Christophe