Subreport binding (GUID) for Related Table in Oracle
I struggled with this....so hopefully the following can save someone else some time.
We have an Oracle backend and have related tables using GlobalID and REL_GlobalID. When using Oracle, the GlobalID is stored as a Char..not an UID so the subrpeort was failing to pull in any related data. There was nothing noted in the documentation about this so it took some troubleshooting.
This is how I was able to get it to work:
- The Parameter on the SubReport was set to GUID and default value was left the same.
- The Parameter for the Query Filter is as follows (note** it is a string not GUID)
The following value had to be set in order for the binding to work: ToStr(Upper('{' + ?REL_GLOBALID + '}' ))
This was the only configuration I was able to find that worked.
-
So Did I @Ali VanSickle? @Amanda Frech? gave me the same formula. Thanks for posting.
0 -
We should have a fix for this coming in the next version (5.9). Watch the release notes for #42230. I've been told that the fix shouldn't break any reports that already have this workaround set up.
0 -
@Amanda Frech? That's good news!
Thanks.
0 -
@Amanda Frech? I have come across another issue. Not sure if it is related to the bug you previously mentioned. Can you confirm?
When multiple features are sent to the report, the subreport only generates for the first record and then repeats the data for all the remaining features. If I set the Parameter in the Sub-Report to 'Multivalue', the report fails to generate. Not sure if I am missing something here or if it is another bug.
0 -
The report seems to work fine in 5.4 with these settings. Once upgraded to 5.8, I also see the subreport only generates for the first record and repeats, as @Ali VanSickle? noted.
@Amanda Frech? - Would it be possible to add this information into the notes for 42230? I assume the fix will resolve this issue, but would require the report configurations to change to using the GUID data type.
0 -
@Ali VanSickle? @Jennifer Di Cesare? I can add those notes to 42230. Do either of you happen to have a public-facing service handy for reproducing that issue? The ones I've got on my end with GUIDs either wouldn't return multiple records from a single GUID, or are using SQL Server instead of Oracle.
Our QA team can probably set something up for testing if needed, but I figure I'll ask in case we can save them some time.
0 -
@Amanda Frech? Sorry all my services are secure.
0 -
@Amanda Frech? - Mine are not public either. Hopefully 5.9 will resolve the issue by switching over to using GUIDs. Any idea of when this should be released?
0 -
@Jennifer Di Cesare? & @Ali VanSickle? 5.9 is likely to be released either next week or the week after.
I've split off a related bug (#43044) for the issue of repeated records in the subreport. But if you could upgrade and re-test within a week or two, you might be able to confirm whether the issue gets resolved with #42230 faster than our QA has a chance to check in on it.
0 -
@Amanda Frech? I can confirm that version 5.9 has fixed the duplicate issue. I had to set the parameter for the Query Filter to GUID instead of the above expression I used and it works great now.
Thanks for the info on this.
0 -
That's great, thanks for the update Ali!
I eventually was able to reproduce the duplicates issue you mentioned (#43044) on my end, but it only happens while you have the workaround applied in the parameter expression. Now that we can go back to the original expression without the workaround, I think the duplicates issue can be avoided.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
11 Kommentare