When the APEX development team at Oracle recently moved to the third early adopters release of APEX 4.0, I panicked! I didn’t see the same “warning emails” that were sent with the previous transition and I thought I had lost some code that I had written for some presentations at the upcoming Kaleidoscope event.
Luckily, that was not the case. The second early adopters release was still available so I was able to export my application an import it into the new release.
During the import I stumbled upon a fantastic new feature that I had not yet known about: Upgrade Application (previously known as the Migration Assistant)!
- You can see the icon available on the right after an application import.
- After clicking the icon you’re taken to an interactive report which lets you know which types of upgrades are available for your application.
- From there you can click on the number associated with the upgrade type to learn more about the upgrade and where it will be applied. Simple check the checkbox where you want to perform the upgrade and click Update. That’s it!
As you can see, taking advantage of some of the great new features of APEX 4.0 will be as easy as 1, 2, 3!
So all your Kaleidoscope demo's are safe? Looking forward to it!
ReplyDeleteCU in a few weeks!
Roel
We are currently upgrading our APEX application from Apex 3.1 version to 4.0. We have done this in two ways .
ReplyDelete1. Upgrade the Apex from 3.1 to 4.0 along with the application
2. Export from 3.1 and import into 4.0 version.
Both the ways we are getting issues
The issues we are getting are:
First method:
1. The reference IDs of fields in tabular form are getting changed and hence the Javascripts are not running.
2. Since the references are changed, the validations have to be re-looked.
We made changes to pick the current reference ids, but still the scripts are not running (not even identified by the system. When we check with Firebug in Firefox, it shows the scripts does not exist/not recognised?!)
Second Method:
1. The reference IDs are changed only for very few.
2. Javascripts are not fully imported by the system and it leaves few scripts. Hence few scripts are missing after import.
Is there something which we are missing?What is the best way to migrate when there are javascripts involved?
Thanks and Regards,
Kuleena
Kuleena,
ReplyDeleteFirst Method:
The IDs changing is an unfortunate issue but doesn't surprise me. Solutions are in the works for future versions of APEX to prevent this from being an issue (you'll reference by name rather than number). For now, you'll just have to fix/test it.
Second Method:
I would be very surprised if scripts were not coming over with the application. That would be a bug that should be reported in the forum.
Regards,
Dan
Dan,
ReplyDeleteThanks for your reply.
We made changes to pick the current reference ids, but still the scripts are not running (not even identified by the system. When we check with Firebug in Firefox, it shows the scripts does not exist/not recognised?!).
The same script is working in 3.1.
Do you know what could be the problem?
Thanks and Regards,
Kuleena
Kuleena,
ReplyDeleteIt's hard to say without access. Can you put it up on apex.oracle.com?
Regards,
Dan
Hi Dan,
ReplyDeleteThanks for the good example!
Looks like some of the sample code links are missing and they are
Here’s a look at some sample JavaScript to handle the AJAX process....
Here is an example DML processes that works with the CLOB in the collection...
Could you please put back those links?
Thank you.
Leo.
Hi Leo,
ReplyDeleteDid you mean to post that here? I'm not sure I follow...
Regards,
Dan