Get your abstracts in for the best conference of 2014 !

We're just in the second half of the 2013 and now we're already talking about "The best conference of 2014"?

Yep! And this conference will be held on Jun 22-26 in Seattle. So I am talking about ODTUG Kscope 14. What else could it be .... And the best conference needs the best preparation. And as content is one of the main things that makes this conference awesome, we need our content lined up as soon as possible. And that's why the call for papers is open now and will be open until October 15 (no extension!). So you still have two months to come up with a subject you're passionate about. If there is something you want to share with the Kscope audience, this is your chance. As we need content for all attendees, from beginner to advanced and for every subject, I am pretty sure you can think of a few things that you can talk about! And this is also an excellent opportunity to dive into a subject and learn yourself: Just submit an abstract of something you want to know more about yourself!

As the Content Lead for the APEX track, I've already selected a team of 12 knowledgable persons that will evaluate all abstracts after October 15 in order to construct the best APEX track ever!

O yeah, did I mention you get a free pass when you're abstract is selected? Makes it even more worthwhile!

See you in Seattle!

For registration, information, submit your abstracts and more, see http://kscope14.com/

Comments

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

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

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

Roels Blog

Search This Blog