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; } } }

How to stop error messages when no rows in dataset

richie.riviere

Hi,
 
I have a BIRT report that has 4 datasets in it. Based on the report parameters I will always hide 3 of these datasets and always show 1.
 
My report works without any issues when the data set that I show returns data. However if my dataset does NOT return any rows on any given execution I get errors at the bottom of the report.
 
I've had this sort of thing before and to fix them I've always rolled back my changes until I could get the report back to a stable state and then work forward to re-implement the changes. I would rather not take this approach if I don't have to because I've made a lot of changes since I last checked in.
 
Can someone help me to try and figure out what the issue might be with the report (i.e. what the errors are telling me) and how I could debug and fix.
 
I have attached a screen shot of the errors in the report as well as a file containing the full stack trace of the report and also the report design file to this post to try and help someone help me.
 
thanks

Find more posts tagged with

Comments

richie.riviere

On doing some more research it looks as if the problem described above is a bug in the BIRT engine code. I have two links to suggest this...
 
<a data-ipb='nomediaparse' href='http://stackoverflow.com/questions/23496980/birt-report-exception-when-zero-results-returned-from-data-set-query'>http://stackoverflow.com/questions/23496980/birt-report-exception-when-zero-results-returned-from-data-set-query</a>
<div> </div>
<a data-ipb='nomediaparse' href='http://developer.actuate.com/community/forum/index.php?/topic/25127-exception-cannot-fetch-the-next-data-row/'>http://developer.actuate.com/community/forum/index.php?/topic/25127-exception-cannot-fetch-the-next-data-row/</a>
 
Can someone tell me in what version of BIRT this bug was fixed? I can't find any notes on the BIRT releases or bugs pages to indicate when it was fixed. Also can anyone tell me if the supposed work around of setting allowNextOnExhaustedResultSet=1 has worked for them? I've tried it and it doesn't seem to work.
 
I am currently using BIRT Designer Version 4.3.1

mwilliams

What type of data set are you using? Your error doesn't seem to be the same as the one where the allowNextOnExhaustedResultSet workaround is suggested. Is this something you can reproduce with the sample database or a data source I can access to run and test on? Or is this only happening with your specific data source?

richie.riviere

I've spent some time today working back through my check ins to find out what differences I had between the last working version of my report and my current version which breaks when an empty dataset is returned.
 
I've found the cause!!
 
In an earlier post on this forum I reported a problem with my report sorting.
 
<a data-ipb='nomediaparse' href='http://developer.actuate.com/community/forum/index.php?/topic/35806-report-not-adhering-to-dataset-sorting/#entry132664'>http://developer.actuate.com/community/forum/index.php?/topic/35806-report-not-adhering-to-dataset-sorting/#entry132664</a>
 
The advice I got was to looks at an Advanced property on my table named 'Sort by groups' and set it to false. I did this and it fixed my sorting however when the resultset in empty I've now learnt that it also causes the errors I have posted.
 
So now that we know the cause can anyone help me with a way to still have my sorting work correctly but also not have an error happen when the resultset is empty.
 
thanks

mwilliams

One thing you could probably do would be to create a running count computed column in your data set and then sort your table by that field. This should put your items back in their original order vs the default ordering. Let me know if that works.

richie.riviere

Thanks for your suggestion. I implemented your solution with a slight variation and it worked for me. I now have both my sorting working and I don't get errors when the resultset is empty.

mwilliams

Great! Glad to help! Let us know whenever you have questions.