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

hiding getImage SEVERE: null

Brodrick Sterling Wiley

Good day, I'm in the process of cleaning up and optimizing my company's report and notice that part of the slowness of generation is coming from a few null images pulled from a dataset (from the Dynamic Image option) with the following error:
 
org.eclipse.birt.report.engine.emitter.EmitterUtil getImage
SEVERE: null
 
The problem is that for these images, some use cases will make it null.
 
I have tried two options for this:
 
1. Making the image element's visibility false if row["URL"] == null with the dataset bound to the image element.
 
2. Had the image element inside a grid element with dataset bound to the grid and making the grid's visibility false if row["URL"] == null, hoping it wouldn't process the image and generate this error
 
Both those attempts still bring up the error in my server's console log.
 
Removing the image element from the template removes the error in my console so it's confirmed that the error is being thrown by this image.
 
Is there a way I can prevent the processing of the image if the dataset's value is null?
 
Thank you in advance for your time

Find more posts tagged with

Comments

Brodrick Sterling Wiley

I hate it when I figure out stuff RIGHT after asking lol
 
For anybody else's reference to the solution,
 
What I did was instead of a grid, I used a table instead, that way if there is a null dataset results, the row will never be processed, hence the image will never be processed either, not giving the undesired error.
 
Of course, set the dataset's query limit 1 if you only want 1 image to be shown at the desired location.