3 Things to consider when upgrading APEX to 23.1

Search for a command to run...

No comments yet. Be the first to comment.
Context is one of the most important things when working with AI. That's kind of the agent "memory" during the session. A key part of the context giving the agent instructions on what to use for speci

A new Data Source was included in this release, you can see it when including a new component, it's called "Sample Data" Some components like maps, charts and Calendar have this source type now, that

This is a great combination for something the used to take some effort on writing some functions to execute actions on specific rows of an IR, like using a hidden page item, assigning the PK value of

Creation of a parallel translated app is no longer the only way to handle multiple languages in APEX. Now under Globalization Attributes, we can select "Text Message-Based" as Translation Method. On

Recently, I created an APP using APEXlang, (check here). I asked the agent to create a lookup table including columns to store colors and icons, useful to work with status for example. The agent no on

Commonly, applications continue working as expected after installing a new version of APEX (thankfully) but sometimes, and often depending on the APEX version you're currently working on, your applications may be impacted, even if compatibility mode is pointing to a previous version.
In a recent upgrade project to APEX 23.1, a few things got my attention. Consider the application was running on the same server, same database, etc. The only changes were the APEX version from 19.2 to 23.1 and refreshing the Universal Theme.
When hiding buttons using a Dynamic Action on Page Load, you can see the button is rendered on the page and then it's hidden.
In this example, the delete button is hidden using a DA, but the user can see it for an instant before it disappears. That's kind of annoying the end user, and it wasn't happening before the upgrade. We also were able to reproduce this in a different server to confirm that it happened after the upgrade.
Because no other action on the page triggers something to show the button back, in this case, the solution is changing the DA for a Server Side Condition, that way the button isn't rendered.



Deprecated DOM Object Dynamic Actions through an error and all javascript code is stopped
This type of Affected Elements were working fine in APEX 19 (Compatibility mode Pre 4.1), but after upgrading you can see the red icon in the Development bar indicating there is a JavaScript error.
So all those DA needed to be changed from DOM Object item, button or jQuery Selector, depending on the case.


Titles on Collapsible regions are now part of the button for collapsing and expanding the region.
In Previous versions, if for some reason you needed to add a link next to the title of the Collapsible region, you could click it. The button tag was in the Controls section of the header, and the title was in a simple div.

In 23, the title is inside a button tag, so if you add a link using an anchor, it won't work.


If you need to do it (and I'm not saying it's a good practice), you could add a closing button tag before the anchor

And that should do the work.

If your link is displayed below the title, you probably need to add this on the inline CSS:
