Skip to main content

Create a PDF document containing dynamic images

For a current project we had the requirement to publish a more or less "glossy" PDF document containing all information about a certain object. One of the bits of information was...an image. 
The first trial we used the APEX_WEB_SERVICE.BLOB2CLOBBASE64 function to convert a Blob to clob with base64 encoding. In the RTF Template (used in Word with the BI Publisher plugin) you can reference it using this code :

<fo:instream-foreign-object content-type="image/jpg">
<xsl:value-of select=".//PHOTO"/>
</fo:instream-foreign-object>
(where PHOTO is the alias of the clob column).

This works....until you're using a slightly bigger picture than a tiny thumbnail. In that case you hit the 32K limit per report column. Although Marc Sewtz (from the APEX Development Team) sort of "promised" to lift this limit in his blogpost of Jun 13 2008 (!) (http://marcsewtz.blogspot.com/2008/06/one-question-about-pdf-printing-feature.html), it is still the current limit.

The workaround - or other approach - is to call an image with a http request in the report definition. Therefore you have to create your own "display_image" procedure that downloads the image. Be sure to grant execute on this procedure to APEX_PUBLIC_USER or ANONYMOUS (depending on your configuration), and modify the WWV_FLOW_EPG_INCLUDE_MOD_LOCAL function when you're using the EPG (see http://daust.blogspot.com/2006/04/xe-calling-stored-procedures.html).

Next, change your query with a call to that procedure:
apex_application.get_g_base_href||'#OWNER#.DISPLAY_IMAGE?P_OBJECT_ID'||ID as IMAGE_URL 

In your RTF Template you have to embed a dummy image and set the "Alt-Text" (via Size in the Image menu) to url:{IMAGE_URL}.

The first result was : It works for HTML output and Excel output...but not for Word (RTF) or PDF. Why this difference? No idea!
My setting was like this:
So the "POPULAIRE_NAAM" was visible on the report, but the image wasn't. And everything else below - all 8 ROWSETS - were visible as well. FYI: The grey border above with the text "Geen afbeelding beschikbaar" is an image itself, so it's not some image missing from this blogpost ;-)
After a lot of trial and error and Googling around, I called to the OTN Forum for help (see thread here : https://forums.oracle.com/forums/thread.jspa?threadID=2347610&tstart=0). After a few hours Carsten Czarski of Oracle Germany pointed to an elaborated example he put on the web - a long time ago, looking at the screen prints : http://www.oracle.com/webfolder/technetwork/de/community/apex/tipps/pdf-dyn-images/index.html. Because it was in German, it never popped up in my Google search..while all the components where in there! So I created a very very simple example to mimic his case. And then the image did show up!
So what did I do wrong?

It seems that the [for-each ROWSET1_ROW] loop must be defined before the image (although in my case that rowset always contains just one entry). It didn't matter for the "POPULAIRE_NAAM" field, but it did for the image (in Word/PDF, not in HTML/Excel).
So the correct setting is:

and now the PDF can contain images of any size....


Comments

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function