Original Message:
Sent: 12/8/2023 12:53:00 PM
From: Steven Shull
Subject: RE: Adding a lookup to a report parameter
Because table domains/automation scripts can impact validation, another option you may want to look at is creating the lookup in the library.xml and specifying the objectname on the table in the dialog that way. I am pretty sure I did something like that in the past to avoid modifying the attribute itself.
------------------------------
Steven Shull
IBM
------------------------------
Original Message:
Sent: 12-08-2023 11:54
From: Stephen Hume
Subject: Adding a lookup to a report parameter
I solved the problem, since out of the box the escalation does not have a lookup, I had to create a table domain and add it to the escalation attribute in database configuration.
------------------------------
Stephen Hume
Sheffield Scientific LLC
Original Message:
Sent: 12-08-2023 10:54
From: Stephen Hume
Subject: Adding a lookup to a report parameter
I have created a BIRT report which will display Escalation Errors over the past 24 hours. I have added "escalation" as a report parameter, and wish to create a lookup that will allow the user to select the escalation they wish to run the report against.
I created a custom lookup in the lookups.xml
Then in the report admistration I added the lookup to the report parameter
The problem is that when I run the report and click on the lookup I am getting "invalid binding" for the three attributes I was hoping to display there.
I know there must be a solution to this and will continue to look for it... just wondering if anyone else can spot what I might be doing incorrectly.
#Reporting
------------------------------
Stephen Hume
Sheffield Scientific LLC
------------------------------