Skip to main content

APEX and Google Visualizations: Create sub-zero dashboards

APEX is cool, Google is cool, Google Visualizations are even cooler. So the combination the coolest technologies available is sub-zero!
A Google Visualization needs can get it's data programmatically by using javascript: create a DataTable object and use addColumn to define the columns and addRows to define the rows. But a Visualization can also be fed with a JSON object. So I created a package prodcure that reads a sql query and spits out a JSON string in the format Google likes. This procedure is called by an APEX On Demand Application Process.
In every APEX page the necessary Google Visualization packages are loaded by calling google.load with some packages, like this:

google.load('visualization', '1', {packages :[ 'geomap', 'intensitymap', 'map' ]});
(The google.load function is loaded in the template by referencing a javascript file http://www.google.com/jsapi).
Every chart is defined as an HTML Region. The source of that Region contains a SQL Statement embedded in a DIV.

<div id="geomap">select 'US-'||cust_state state, sum(order_total) OrderTotal
from demo_customers c, demo_orders o
where o.customer_id = c.customer_id
group by cust_state</div>
In the Region Footer the JSON string is pulled using a getData function. That function calls the PL/SQL JSON-generator procedure that fetches the SQL query from the APEX Repository. Subsequently two simple calls are enough to replacing the SQL query with the Google chart.

<script type="text/javascript">
$s('geomap',null)
var data = getData('#REGION_ID#');
var geomap = new google.visualization.GeoMap($x('geomap'));
var options = {};
options['region'] = 'US';
options['width'] = '300px';
options['height'] = '300px';
geomap.draw(data, options);
</script>
On the Google Visualization website the expected data (number of columns and type) are described for every type of chart. By just entering a SQL Statement that corresponds with the Google specs, I can produce any Google Visualization within seconds (once the SQL is correct ;-) )!
You can experience the APEX-Google Visualization live on apex.oracle.com.

Why would you use Google Visualizations (apart from "just because we can")? If your needs are fulfilled using the standard APEX / AnyChart stuff, there is no need. But there are some charts, especially the animated, time related, charts that are sooo cool and AnyCharts doesn't contain all the charts Google does (and vice versa). And I guess the number of Google Visualizations will grow, as everyone can add gadgets to that library.

Comments

Denes Kubicek said…
Nice posting Roel.

Denes
Stew said…
I like the "just because we can" reason best! How about "cuz it looks way cooler than the AnyCharts"? Or "to impress our programmer friends"? Or "job security, cuz no one understands this stuff better than me!"?

;-)

Thanks for sharing this, providing a path for new learning for the next year into Google Visualizations!
Stew said…
Ooo, I just saw the org chart! When I saw what happens when you double-click on a parent node, I said "NFW"! :-)

That is so slick!
Patrick Wolf said…
Looks really nice!
Joel R. Kallman said…
Roel,

This is very cool (or as you say, "sub-zero").

Joel
Louis-Guillaume said…
Roel,
I really love this API!

You can see examples I made for the integration of Google Visualization API.

http://www.lgcarrier.com/2008/12/google-visualization-api-organizational.html

http://www.lgcarrier.com/2008/11/google-visualization-api.html

Have a nice day,
Louis-Guillaume
Anonymous said…
Can you please give me the complete details of what needs to go where in the page header, region Source and region footer to check this out on my apex pages. This can do wonders for my analysis.
Roel said…
@Anonymous:

Page Header (or template) : google.load('visualization', '1', {packages :[ 'geomap', 'intensitymap', 'map' ]});

Region Source:
<div id="geomap">select 'US-'||cust_state state, sum(order_total) OrderTotal
from demo_customers c, demo_orders o
where o.customer_id = c.customer_id
group by cust_state</div>
Region Footer:
$s('geomap',null)
var data = getData('#REGION_ID#');
var geomap = new google.visualization.GeoMap($x('geomap'));
var options = {};
options['region'] = 'US';
options['width'] = '300px';
options['height'] = '300px';
geomap.draw(data, options);

And then there is the getData function. That one calls a DB-procedure that spits out the JSON string result from the query in the Region Source. And that code is not in the blog post...
However you can use the package on apex.oracle.com in your own Application Process by calling roel.apex_gv.generate_visualization( p_region_id ); (I granted an execute to public).

HTH - a little,
Roel

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