Skip to main content

ODTUG: Wednesday

This day started off with a very nice presentation about the joys of Javascript by Dan "The Man"McGhan. In a very nice pace he took the audience by the hand and increased the difficulty level step-by-step. His key message was; Don't be scared of Javascript, because if you look close enough it is looks more like PL/SQL than you might think at first sight. Get to learn jQuery and do your thing!
Another nice presentation was about "RESTful Web Services" by Jason Straub. He demoed how you can use webservices withing APEX to manage the buckets and contents on an Amazon S3 cloud environment. He also pointed out that not only APEX can consume webservices, but also can act as the source of a webservice. In order to achieve that you have to create a report on a public page that returns either XML or Json. He didn't show a demo, but promised to get out a paper or how-to out there next week. Have to try that myself soon!
Another fine session was Tim St. Hilaire's session on "APEX and AJAX". Nice examples on how to handcode your Ajax processes (the 'old' way) and how to new Dynamic Actions to do it the APEX 4-way.
Then, finally, it was my turn to show the coolest Plug-In of the conference - at least, that's my humble opinion ;-). Around 60 - 70 people showed up and the presentation went very well. ended right on time again!
After that, I didn't have the energy to attend another session and just had a beer at the bar with some other Europeans (Debra, Alex, Marco, Jonathan, Tim etc).
Then it was time for the "big party": good food, more than enough drinks and a very good comedian (John Heffron). After some more drinks in the Presedentail Suite (thanks Mike Riley) it was time to head off to bed....

Comments

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...

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 ...

Caution when using Suppress Change Event on an Interactive Grid Column

There are some, maybe rare, use case when you want to set the " Suppress Change Event " switch of a Dynamic Action to " Yes ". Usually that's only necessary when the Dynamic Action is fired On Change  and executes a Set Value  with the same field as a target. There might be a chain of events leading to this or just one. If you forget to set it you'll end up in an endless loop and your browser will choke. That works all fine and as expected with regular Page Items. However ... when you apply this to a column in an Interactive Grid something unexpected happens. When you set the Suppress Change Event of a Dynamic Action that fires on change of a column to Yes , the value of that item seems empty when you leave that field (column)! If you navigate back into that field, the (new) value does show up... You can call it a feature, you can call it a bug, but bottom line it is unexpected and undesired behaviour. The solution is to call the Grid method SetActiv...