This content has been marked as final. Show 2 replies
Hi Haakon,1 person found this helpful
single component export/import is only supported for application which are identical on the source and target system. It relies on the fact that other referenced components (for example user interface, templates, ...) use the same IDs on body systems.
Because of the APEX 4.2 upgrade, that's not the case anymore. As part of the upgrade, several new components had to be created on the fly which do now have different IDs on dev and prod. That's why the single component export/import doesn't work anymore.
If the single component export/import is used to patch applications, it's recommended to do a full export of the app on dev and import it into prod after upgrading to a newer version of APEX to make sure that body systems are using the same component IDs. After that your single component deployment should work as before.
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Ok, thanks Patrick.
I understand the reason behind this problem. I guess we've been spoiled so far with the ease and simplicity in which Apex has worked. Few to none issues with upgrades and installations.
In a perfect world, we should be able to retire a complete production version of an application and replace it with a new baseline from the development server. Unfortunately that's not always the case in the real world.
Due to infrastructure/network/shares/database differences there's sometimes a need for minor code changes when components are propagated to production. In any programmers bible this is ideally a big no-no of course, but sometimes the extra code to handle such issues is just not worth it on smaller applications. Guess this forces us to do that extra coding now :-)