This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
Invalid bound column name:
Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
We are having similar problems.
There is an export/import tool that came with the upgrade (errored out a lot, as all reports are available, but not all are licensed).
What we have done:
Opened the report in the new version of BIRT - make changes if necessary, then recompile, import into Maximo and generate the request page.
Major problems were with PO reports and also any that print landscape.
Pat Morrow
pmorrow8@yahoo.com
________________________________
From: e11271b <ebennett@gfs.com>
To: MAXIMO@yahoogroups.com
Sent: Tuesday, November 6, 2012 6:00 AM
Subject: [MAXIMO List] BIRT Reports Do not work after upgrading to 3.7.1
We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
Invalid bound column name:
Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
I am working on a specific custom report that was developed from scratch in 232.
Now in my new 371 development environment, I'm getting a ton of invalid bound column errors. Even though the bindings look ok.
It looks like the biggest issue is with the aggregate fields. I can remove the field and create a new aggregate entry, but I still get an invalid bound column error.
This tool that came with the upgrade, do you run that against custom reports?
--- In MAXIMO@yahoogroups.com, Pat Morrow <pmorrow8@...> wrote:
>
> We are having similar problems.
> Â
> There is an export/import tool that came with the upgrade (errored out a lot, as all reports are available, but not all are licensed).
> Â
> What we have done:
> Opened the report in the new version of BIRT - make changes if necessary, then recompile, import into Maximo and generate the request page.
> Â
> Major problems were with PO reports and also any that print landscape.
>
> Pat Morrow
> pmorrow8@...
>
>
>
> ________________________________
> From: e11271b <ebennett@...>
> To: MAXIMO@yahoogroups.com
> Sent: Tuesday, November 6, 2012 6:00 AM
> Subject: [MAXIMO List] BIRT Reports Do not work after upgrading to 3.7.1
>
>
> Â
>
> We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
>
> Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
>
> Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
>
> Invalid bound column name:
>
> Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
>
> If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
>
> Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
>
>
>
>
>
>
I worked with a site that was having problems that sound similar to what you're describing. We finally found out the report writer was so excited with the upgrade that the writer grabbed files from the wrong folder during the BIRT Report Designer setup.
Look at pages 8-14 of the PDF from IBM to make sure the Report Designer is setup correctly.
http://www-01.ibm.com/support/docview.wss?uid=swg21605970
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> I am working on a specific custom report that was developed from scratch in 232.
>
> Now in my new 371 development environment, I'm getting a ton of invalid bound column errors. Even though the bindings look ok.
>
> It looks like the biggest issue is with the aggregate fields. I can remove the field and create a new aggregate entry, but I still get an invalid bound column error.
>
> This tool that came with the upgrade, do you run that against custom reports?
>
>
>
> --- In MAXIMO@yahoogroups.com, Pat Morrow <pmorrow8@> wrote:
> >
> > We are having similar problems.
> > Â
> > There is an export/import tool that came with the upgrade (errored out a lot, as all reports are available, but not all are licensed).
> > Â
> > What we have done:
> > Opened the report in the new version of BIRT - make changes if necessary, then recompile, import into Maximo and generate the request page.
> > Â
> > Major problems were with PO reports and also any that print landscape.
> >
> > Pat Morrow
> > pmorrow8@
> >
> >
> >
> > ________________________________
> > From: e11271b <ebennett@>
> > To: MAXIMO@yahoogroups.com
> > Sent: Tuesday, November 6, 2012 6:00 AM
> > Subject: [MAXIMO List] BIRT Reports Do not work after upgrading to 3.7.1
> >
> >
> > Â
> >
> > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> >
> > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> >
> > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> >
> > Invalid bound column name:
> >
> > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> >
> > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> >
> > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> >
> >
> >
> >
> >
> >
>
I'm working on a local machine where the libraries and templates where copied over from the max7.5.0.3 birt environment and referenced locally in eclipse.
I started fooling around with one of the fields that was identified as having invalid column bindings, and found that if I remove the reference to an outer field I don't get that error..
This causes an invalid column binding error.
dataSetRow["OWNER"]==row._outer["EMPLOYEENUMBER"]
This doesn't.
dataSetRow["OWNER"]=='12345'
I let the expression build create the original expression, so I'm not sure whats wrong with it.
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> I worked with a site that was having problems that sound similar to what you're describing. We finally found out the report writer was so excited with the upgrade that the writer grabbed files from the wrong folder during the BIRT Report Designer setup.
>
> Look at pages 8-14 of the PDF from IBM to make sure the Report Designer is setup correctly.
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21605970
>
>
> --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> >
> > I am working on a specific custom report that was developed from scratch in 232.
> >
> > Now in my new 371 development environment, I'm getting a ton of invalid bound column errors. Even though the bindings look ok.
> >
> > It looks like the biggest issue is with the aggregate fields. I can remove the field and create a new aggregate entry, but I still get an invalid bound column error.
> >
> > This tool that came with the upgrade, do you run that against custom reports?
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, Pat Morrow <pmorrow8@> wrote:
> > >
> > > We are having similar problems.
> > > Â
> > > There is an export/import tool that came with the upgrade (errored out a lot, as all reports are available, but not all are licensed).
> > > Â
> > > What we have done:
> > > Opened the report in the new version of BIRT - make changes if necessary, then recompile, import into Maximo and generate the request page.
> > > Â
> > > Major problems were with PO reports and also any that print landscape.
> > >
> > > Pat Morrow
> > > pmorrow8@
> > >
> > >
> > >
> > > ________________________________
> > > From: e11271b <ebennett@>
> > > To: MAXIMO@yahoogroups.com
> > > Sent: Tuesday, November 6, 2012 6:00 AM
> > > Subject: [MAXIMO List] BIRT Reports Do not work after upgrading to 3.7.1
> > >
> > >
> > > Â
> > >
> > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > >
> > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > >
> > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > >
> > > Invalid bound column name:
> > >
> > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > >
> > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > >
> > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
Can you post the select statement from the dataset Open method?
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> I'm working on a local machine where the libraries and templates where copied over from the max7.5.0.3 birt environment and referenced locally in eclipse.
>
> I started fooling around with one of the fields that was identified as having invalid column bindings, and found that if I remove the reference to an outer field I don't get that error..
>
> This causes an invalid column binding error.
> dataSetRow["OWNER"]==row._outer["EMPLOYEENUMBER"]
>
> This doesn't.
> dataSetRow["OWNER"]=='12345'
>
> I let the expression build create the original expression, so I'm not sure whats wrong with it.
>
>
>
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > I worked with a site that was having problems that sound similar to what you're describing. We finally found out the report writer was so excited with the upgrade that the writer grabbed files from the wrong folder during the BIRT Report Designer setup.
> >
> > Look at pages 8-14 of the PDF from IBM to make sure the Report Designer is setup correctly.
> >
> > http://www-01.ibm.com/support/docview.wss?uid=swg21605970
> >
> >
> > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > >
> > > I am working on a specific custom report that was developed from scratch in 232.
> > >
> > > Now in my new 371 development environment, I'm getting a ton of invalid bound column errors. Even though the bindings look ok.
> > >
> > > It looks like the biggest issue is with the aggregate fields. I can remove the field and create a new aggregate entry, but I still get an invalid bound column error.
> > >
> > > This tool that came with the upgrade, do you run that against custom reports?
> > >
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, Pat Morrow <pmorrow8@> wrote:
> > > >
> > > > We are having similar problems.
> > > > Â
> > > > There is an export/import tool that came with the upgrade (errored out a lot, as all reports are available, but not all are licensed).
> > > > Â
> > > > What we have done:
> > > > Opened the report in the new version of BIRT - make changes if necessary, then recompile, import into Maximo and generate the request page.
> > > > Â
> > > > Major problems were with PO reports and also any that print landscape.
> > > >
> > > > Pat Morrow
> > > > pmorrow8@
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: e11271b <ebennett@>
> > > > To: MAXIMO@yahoogroups.com
> > > > Sent: Tuesday, November 6, 2012 6:00 AM
> > > > Subject: [MAXIMO List] BIRT Reports Do not work after upgrading to 3.7.1
> > > >
> > > >
> > > > Â
> > > >
> > > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > > >
> > > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > > >
> > > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > > >
> > > > Invalid bound column name:
> > > >
> > > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > > >
> > > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > > >
> > > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
You Bet!!
##### SQL FOR DATA IN CHILD TABLE
sqlText = "" +
"SELECT DISTINCT " +
" WO.WONUM, " +
" WO.STATUS, " +
" WO.WORKTYPE, " +
" WO.DESCRIPTION, " +
" COUNT(JPT.WONUM) OVER(PARTITION BY WO.WONUM) AS JOBPLANTASKS, " +
" COUNT(JPTC.WONUM) OVER(PARTITION BY WO.WONUM) AS JOBPLANTASKSCOMPLETE, " +
" to_date(to_char(WO.TARGSTARTDATE, 'MM/DD/YYYY'),'MM/DD/YYYY') as TARGSTARTDATE, " +
" to_date(to_char(WO.ACTSTART, 'MM/DD/YYYY'),'MM/DD/YYYY') AS ACTSTART, " +
" to_date(to_char(WO.ACTFINISH, 'MM/DD/YYYY'),'MM/DD/YYYY') AS ACTFINISH, " +
" SUBSTR(wo.glaccount, 0, INSTR(wo.glaccount, '-')-1) AS SITEID, " +
" WO.OWNER as OWNER, " +
" WO.GFSINSPECTIONSTATUS, " +
" WO.GFSINSPECTIONDATE " +
"FROM WORKORDER WO " +
" INNER JOIN FINANCIALPERIODS FP " +
" ON FP.FINANCIALPERIOD = '"+params["financialPeriod"]+"' " +
" LEFT OUTER JOIN WORKORDER JPT " +
" ON JPT.WONUM = WO.WONUM " +
" LEFT OUTER JOIN WORKORDER JPTC " +
" ON JPTC.WONUM = WO.WONUM " +
" AND JPTC.WONUM = JPT.WONUM " +
" AND (JPTC.STATUS = 'COMP' OR JPTC.STATUS = 'CLOSE') " +
"WHERE " +
" WO.ACTSTART >= FP.PERIODSTART " +
" AND WO.ACTFINISH <= FP.PERIODEND " +
" AND WO.GLACCOUNT LIKE '"+department+"' " +
" AND WO.WOCLASS = 'WORKORDER' " +
" AND (WO.PMNUM is not null OR WO.GFSINSPECTIONSTATUS is not null)";
row["WONUM"] = pmDataSet.getString("WONUM");
row["STATUS"] = pmDataSet.getString("STATUS");
row["WORKTYPE"] = pmDataSet.getString("WORKTYPE");
row["DESCRIPTION"] = pmDataSet.getString("DESCRIPTION");
row["JOBPLANTASKS"] = pmDataSet.getInteger("JOBPLANTASKS");
row["JOBPLANTASKSCOMPLETE"] = pmDataSet.getInteger("JOBPLANTASKSCOMPLETE");
row["TARGETSTARTDATE"] = pmDataSet.getTimestamp("TARGSTARTDATE");
row["ACTSTART"] = pmDataSet.getTimestamp("ACTSTART");
row["ACTFINISH"] = pmDataSet.getTimestamp("ACTFINISH");
row["SITEID"] = pmDataSet.getString("SITEID");
row["OWNER"] = pmDataSet.getString("OWNER");
row["GFSINSPECTIONSTATUS"] = pmDataSet.getString("GFSINSPECTIONSTATUS");
row["GFSINSPECTIONDATE"] = pmDataSet.getTimestamp("GFSINSPECTIONDATE");
row["FINISHEDONTIME"] = pmDataSet.getTimestamp("ACTFINISH") != null &&
(BirtDateTime.diffDay(pmDataSet.getTimestamp("TARGSTARTDATE"),pmDataSet.getTimestamp("ACTFINISH")) > 7);
##### SQL FOR DATA IN PARENT TABLE
sqlText = "" +
"select " +
" to_char(A.EMPLOYEE_NBR) as EMPLOYEE_NBR, " +
" P.DISPLAYNAME, " +
" P.LOCATION AS SITE, " +
" A.WEEK_ENDING, " +
" LABOR_HOURS, " +
" VACATION_HOURS, " +
" SICK_HOURS,TIMEOFF_HOURS, " +
" HOLIDAY_HOURS, " +
" EXCEPTION_HOURS, " +
" CASE ISMECHANIC.GROUPNAME WHEN 'MECHANIC' THEN 'TRUE' ELSE 'FALSE' END AS ISMECHANIC, " +
" CASE ISINVENTORY.GROUPNAME WHEN 'INVENTORY' THEN 'TRUE' ELSE 'FALSE' END AS ISINVENTORY, " +
" CASE ISCUSTODIAN.GROUPNAME WHEN 'CUSTODIAN' THEN 'TRUE' ELSE 'FALSE' END AS ISCUSTODIAN " +
"FROM " +
" WCS_ADMIN.VW_MAXIMO_EMPLOYEE_TIME A " +
" LEFT OUTER JOIN PERSON P ON P.PERSONID = to_char(A.EMPLOYEE_NBR) " +
" LEFT OUTER JOIN GROUPUSER ISMECHANIC ON ISMECHANIC.USERID = to_char(A.EMPLOYEE_NBR) AND ISMECHANIC.GROUPNAME = 'MECHANIC' " +
" LEFT OUTER JOIN GROUPUSER ISINVENTORY ON ISINVENTORY.USERID = to_char(A.EMPLOYEE_NBR) AND ISINVENTORY.GROUPNAME = 'INVENTORY' " +
" LEFT OUTER JOIN GROUPUSER ISCUSTODIAN ON ISCUSTODIAN.USERID = to_char(A.EMPLOYEE_NBR) AND ISCUSTODIAN.GROUPNAME = 'CUSTODIAN' " +
" INNER JOIN FINANCIALPERIODS FP ON FP.FINANCIALPERIOD = '"+params["financialPeriod"]+"' " +
"WHERE " +
" (A.WEEK_ENDING >= FP.PERIODSTART and A.WEEK_ENDING <= FP.PERIODEND) " +
"AND " +
" P.LOCATION IS NOT NULL AND P.LOCATION LIKE '"+department+"%' " +
"ORDER BY " +
" A.EMPLOYEE_NBR, A.WEEK_ENDING";
row["EMPLOYEENUMBER"] = attendanceDataSet.getString("EMPLOYEE_NBR");
row["DISPLAYNAME"] = attendanceDataSet.getString("DISPLAYNAME");
row["SITE"] = attendanceDataSet.getString("SITE");
row["WEEKENDING"] = attendanceDataSet.getDate("WEEK_ENDING");
row["LABORHOURS"] = attendanceDataSet.getFloat("LABOR_HOURS");
row["VACATIONHOURS"] = attendanceDataSet.getFloat("VACATION_HOURS");
row["SICKHOURS"] = attendanceDataSet.getFloat("SICK_HOURS");
row["TIMEOFFHOURS"] = attendanceDataSet.getFloat("TIMEOFF_HOURS");
row["HOLIDAYHOURS"] = attendanceDataSet.getFloat("HOLIDAY_HOURS");
row["EXCEPTIONHOURS"] = attendanceDataSet.getFloat("EXCEPTION_HOURS");
row["ISMECHANIC"] = attendanceDataSet.getString("ISMECHANIC")
row["ISINVENTORY"] = attendanceDataSet.getString("ISINVENTORY");
row["ISCUSTODIAN"] = attendanceDataSet.getString("ISCUSTODIAN");
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
>
> Can you post the select statement from the dataset Open method?
>
> --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> >
> > I'm working on a local machine where the libraries and templates where copied over from the max7.5.0.3 birt environment and referenced locally in eclipse.
> >
> > I started fooling around with one of the fields that was identified as having invalid column bindings, and found that if I remove the reference to an outer field I don't get that error..
> >
> > This causes an invalid column binding error.
> > dataSetRow["OWNER"]==row._outer["EMPLOYEENUMBER"]
> >
> > This doesn't.
> > dataSetRow["OWNER"]=='12345'
> >
> > I let the expression build create the original expression, so I'm not sure whats wrong with it.
> >
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > >
> > > I worked with a site that was having problems that sound similar to what you're describing. We finally found out the report writer was so excited with the upgrade that the writer grabbed files from the wrong folder during the BIRT Report Designer setup.
> > >
> > > Look at pages 8-14 of the PDF from IBM to make sure the Report Designer is setup correctly.
> > >
> > > http://www-01.ibm.com/support/docview.wss?uid=swg21605970
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > >
> > > > I am working on a specific custom report that was developed from scratch in 232.
> > > >
> > > > Now in my new 371 development environment, I'm getting a ton of invalid bound column errors. Even though the bindings look ok.
> > > >
> > > > It looks like the biggest issue is with the aggregate fields. I can remove the field and create a new aggregate entry, but I still get an invalid bound column error.
> > > >
> > > > This tool that came with the upgrade, do you run that against custom reports?
> > > >
> > > >
> > > >
> > > > --- In MAXIMO@yahoogroups.com, Pat Morrow <pmorrow8@> wrote:
> > > > >
> > > > > We are having similar problems.
> > > > > Â
> > > > > There is an export/import tool that came with the upgrade (errored out a lot, as all reports are available, but not all are licensed).
> > > > > Â
> > > > > What we have done:
> > > > > Opened the report in the new version of BIRT - make changes if necessary, then recompile, import into Maximo and generate the request page.
> > > > > Â
> > > > > Major problems were with PO reports and also any that print landscape.
> > > > >
> > > > > Pat Morrow
> > > > > pmorrow8@
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: e11271b <ebennett@>
> > > > > To: MAXIMO@yahoogroups.com
> > > > > Sent: Tuesday, November 6, 2012 6:00 AM
> > > > > Subject: [MAXIMO List] BIRT Reports Do not work after upgrading to 3.7.1
> > > > >
> > > > >
> > > > > Â
> > > > >
> > > > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > > > >
> > > > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > > > >
> > > > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > > > >
> > > > > Invalid bound column name:
> > > > >
> > > > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > > > >
> > > > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > > > >
> > > > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Just an update..
One of the issue appear to be related to the row._outer in some filter expressions.
For the will work without throwing the invalid column binding error.
dataSetRow["OWNER"] == '12345'
But, when you reference the row._outer... I get an invalid column binding error.
dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
>
> Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
>
> Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
>
> Invalid bound column name:
>
> Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
>
>
> If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
>
> Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
>
Just an update..
One of the issue appear to be related to the row._outer in some filter expressions.
For the will work without throwing the invalid column binding error.
dataSetRow["OWNER"] == '12345'
But, when you reference the row._outer... I get an invalid column binding error.
dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
>
> Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
>
> Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
>
> Invalid bound column name:
>
> Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
>
>
> If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
>
> Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
>
also,, I added a data field and entered row._outer["EMPLOYEENUMBER"] as the expression.
The report runs and displays the result correctly. So, it appears to be related to the comparison.
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> Just an update..
>
> One of the issue appear to be related to the row._outer in some filter expressions.
>
> For the will work without throwing the invalid column binding error.
>
> dataSetRow["OWNER"] == '12345'
>
> But, when you reference the row._outer... I get an invalid column binding error.
>
> dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
>
>
>
>
> --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> >
> > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> >
> > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> >
> > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> >
> > Invalid bound column name:
> >
> > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> >
> >
> > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> >
> > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> >
>
Happy to see you worked it out.
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> also,, I added a data field and entered row._outer["EMPLOYEENUMBER"] as the expression.
>
> The report runs and displays the result correctly. So, it appears to be related to the comparison.
>
>
>
> --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> >
> > Just an update..
> >
> > One of the issue appear to be related to the row._outer in some filter expressions.
> >
> > For the will work without throwing the invalid column binding error.
> >
> > dataSetRow["OWNER"] == '12345'
> >
> > But, when you reference the row._outer... I get an invalid column binding error.
> >
> > dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
> >
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > >
> > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > >
> > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > >
> > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > >
> > > Invalid bound column name:
> > >
> > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > >
> > >
> > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > >
> > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > >
> >
>
I'ts not worked out. I just took out to row._outer reference to see if that was causing the issue. And it was. The issue remains, since I need to reference data from the parent table.
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> Happy to see you worked it out.
>
> --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> >
> > also,, I added a data field and entered row._outer["EMPLOYEENUMBER"] as the expression.
> >
> > The report runs and displays the result correctly. So, it appears to be related to the comparison.
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > >
> > > Just an update..
> > >
> > > One of the issue appear to be related to the row._outer in some filter expressions.
> > >
> > > For the will work without throwing the invalid column binding error.
> > >
> > > dataSetRow["OWNER"] == '12345'
> > >
> > > But, when you reference the row._outer... I get an invalid column binding error.
> > >
> > > dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
> > >
> > >
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > >
> > > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > > >
> > > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > > >
> > > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > > >
> > > > Invalid bound column name:
> > > >
> > > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > > >
> > > >
> > > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > > >
> > > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > > >
> > >
> >
>
Then let's back up a bit. Couple of questions:
How many data sets are you using for the report?
Are you using any parameters to help in record selection?
--- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@...> wrote:
>
> I'ts not worked out. I just took out to row._outer reference to see if that was causing the issue. And it was. The issue remains, since I need to reference data from the parent table.
>
>
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Happy to see you worked it out.
> >
> > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > >
> > > also,, I added a data field and entered row._outer["EMPLOYEENUMBER"] as the expression.
> > >
> > > The report runs and displays the result correctly. So, it appears to be related to the comparison.
> > >
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > >
> > > > Just an update..
> > > >
> > > > One of the issue appear to be related to the row._outer in some filter expressions.
> > > >
> > > > For the will work without throwing the invalid column binding error.
> > > >
> > > > dataSetRow["OWNER"] == '12345'
> > > >
> > > > But, when you reference the row._outer... I get an invalid column binding error.
> > > >
> > > > dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
> > > >
> > > >
> > > >
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > > >
> > > > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > > > >
> > > > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > > > >
> > > > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > > > >
> > > > > Invalid bound column name:
> > > > >
> > > > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > > > >
> > > > >
> > > > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > > > >
> > > > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > > > >
> > > >
> > >
> >
>
To recreate the scenario all you need is a simple report with a table using dataSet1, that contains a data field and a table with an aggregation using dataSet2.
The data field in the parent table is a string, and the aggregate value is also a string.
Then from the child table, you just have to filter the aggregation referencing the data field in the parent table. BIRT will create that link using a row._outer[].
This will fail, and you just have to replace the row._outer[] with a hard coded value such as '1234' to eliminate the error(s).
I created a work around by poplating a global variable when the parent table sets the data field that I was linking to. I am now using this global variable in the child tables aggregations filter expression. It's a hack, but appears to work.
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> Then let's back up a bit. Couple of questions:
>
> How many data sets are you using for the report?
> Are you using any parameters to help in record selection?
>
>
> --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> >
> > I'ts not worked out. I just took out to row._outer reference to see if that was causing the issue. And it was. The issue remains, since I need to reference data from the parent table.
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > >
> > > Happy to see you worked it out.
> > >
> > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > >
> > > > also,, I added a data field and entered row._outer["EMPLOYEENUMBER"] as the expression.
> > > >
> > > > The report runs and displays the result correctly. So, it appears to be related to the comparison.
> > > >
> > > >
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > > >
> > > > > Just an update..
> > > > >
> > > > > One of the issue appear to be related to the row._outer in some filter expressions.
> > > > >
> > > > > For the will work without throwing the invalid column binding error.
> > > > >
> > > > > dataSetRow["OWNER"] == '12345'
> > > > >
> > > > > But, when you reference the row._outer... I get an invalid column binding error.
> > > > >
> > > > > dataSetRow["OWNER"] == row._outer["EMPLOYEENUMBER"]
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "e11271b" <ebennett@> wrote:
> > > > > >
> > > > > > We moved from Maximo 7.1 to 7.5.0.3. Along with this we upgraded our BIRT development environment from 2.3.2 to 3.7.1.
> > > > > >
> > > > > > Now those reports that were created using BIRT 2.3.2 are no longer working. From eclipse when you preview, I get a ton of errors, including...
> > > > > >
> > > > > > Wrapped java.lang.UnsupportedOperationException: Page break can not be set at render time.
> > > > > >
> > > > > > Invalid bound column name:
> > > > > >
> > > > > > Script engine error: The outer query results does not exist. This might be caused by a "_outer" reference in a query without parent query.
> > > > > >
> > > > > >
> > > > > > If I simply move the report design file back to the BIRT 2.3.2 development environment the report runs as expected.
> > > > > >
> > > > > > Are reports created in 2.3.2 not compatible with the 3.7.1 engine?
> > > > > >
> > > > >
> > > >
> > >
> >
>