Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.3K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 466 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Page Export from one workspace to another
I have three environments currently Dev, Test, Preproduction (UAT). I'm able to export and import freely entire applications up the deployment chain but get error when trying to move a single page export from one environment to another. This seems like a limitation to this developer, as there are cases and situations where I want to only deploy a single page up the environment stack.
Comments
-
I guess you made a mistake when creating the test and production workspaces. You shouldn't create a new workspace for test and production. Instead, export your development workspace and import it in test and production. That way you keep the unique id's the same in all environments.
You can export and import whole applications in another workspace, because an offset is used when importing an application to generate the new id's. That won't work with a single page.
-
Got It thanks, I wasn't the original developer, workspace names are the same, what would be different? Seems like a bad design from the get go, that pages can't be imported into different workspaces. BTW, everything is the same in all environment workspaces. Update Just confirmed that workspaces were not exported/imported to upper environments. Deciding whether to rebuild, I don't want to export entire app just for a simple page update.
-
workspace names are the same, what would be different?
The workspace ID. When you create a new workspace in APEX Builder, it generates a new ID. When you import an exported workspace, it keeps the ID.
