Community
Participate
Working Groups
Create a simple grouped report using the CUSTOMERS table from the Classic Models database. Use Country and State as the groups. Next, decide to experiment with the difference between a key of dataSetRow["STATE"] and row["STATE"]. But, type the key as row["state"]. Run the report. This won't work. But, the error is: The following items have errors: ReportDesign (id = 1): + Column binding "state" does not exist Notice that the error is attributed to the report design. Now, give the report to another person to sort out. They'll look on the report design (as suggested by the error), but won't see any bindings. The workaround is to search the XML source for the word "state", and you'll find the offending group key. However, this is not terribly obvious. Expected the error to say something like: Column binding "state" does not exist Referenced from the GroupKey property of TableGroup "State" (Or whatever the correct property and element names are.) Even better, expected the error to appear in the Problems list so I could click on it and have the offending component selected.
Does clicking "+" give more details? Or I think Dte may need provide more detailed error message.
This actually ask DtE for providing context info when evaluate a script. The whole part is missing in current data engine script evaluation framework.
(In reply to comment #2) > This actually ask DtE for providing context info when evaluate a script. The > whole part is missing in current data engine script evaluation framework. Does engine know the context, such as the report item, the event, or the databinding column name, or a high lighting rule when it evaluates a JS expression? THis way, when an JS eval error is get, BIRT engine can tell user which report item and what kind of calcuation is being evaluated when an error happen?
Set the component to Report Engine. If engine can help to the point listed in #3 please make corresponding changes. Otherwise please assign the bug back to data engine.
Each script have a unique ID and associated with the unique line in the report design, the designer uses that ID to locate the errors with the report design file. The DTE need use the ID to run the script.
Similar to 247938, the assignation of script id needs lots of changes in data engine.Suggest to fix in 2.5.2.
