UI Defaults Import problems and best practice for using UI defaults

Question

Hi,
I'm hoping some of you experts can tell me how to Import the UI Defaults from Schema A and Workspace A to Schema B and Workspace B. My goal is to fluidly share the UI defaults with another developer as we march forward creating new versions of the application (inside new Workspaces with new schema names). My longer term goal was to create a "library" of UI defaults that other future developers could easily access as well.
The basic setup I have been using is that each developer gets their own schema and their own workspace. When a new version of the database design is made, I keep the older versions of the workspaces and schemas intact and then create a new workspace and new schema for each developer (just two of us right now). Then we Export apps, respectively, from our old workspaces and Import apps into our new workspaces. I also create a new db tablespace and new db user account and map to new workspace as well. This way I always know what db design version we are using against what Apex app version and can, conversely, delete tablespaces, user accounts, workspaces and Apex schemas in one swallow without worrying about getting the wrong version of something accidentally deleted. 9It may seem like I am doing a lot of extra work, but my sanity is still (relatively) intact.)
I keep getting
"ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-20001: You do not have access to the schema that you are importing. Import failed. <pre>begin wwv_flow_api.g_id_offset := 0; wwv_flow_hint.g_schema := 'MY_OTHER_SCHEMA'; wwv_flow_hint.check_schema_privs; end;</pre>"
when I try importing it.
We want to share our UI defaults that we each set up in our respective workspaces and schemas. We do have some overlap of tables (which may be a no no I suppose). We also each have differently named (test) apps.
So, like app Import/Export, I thought I could just Export my app (along with UI) from Schema A and Workspace A and simply import it into Schema B and Workspace B and then in the new Workspace have access to the UI. I tried editing the UI *.SQL using the app ID and new schema name but it still balks. It seems like there is an internal table ID code specific to each table that is particular to the table and the workspace it was created in.
I can go to a specific workspace, create a sample UI, Export it's app, and Import the same app (new ID) into same workspace and the UI shows up fine.
So, what good is the UI defaults if you can't carry them forward to the next version of your app that is in a new workspace? It seems like we are forced into creating the equivalent of one workspace, say the "Library", and both of us with separate schemas sign into here. But then how do I get the UIs from the "Library" to our "Beta" workspace, and similarly from there to 'Production' without recreating UIs each time? And, if I prefer a sample set of records, say only 100 test recs, and the other developer prefers a full set, say 30,000 recs, and we have to use the same workspace, since the workspace can only be associated with one db tablespace, how can I load both 100 and 30,000 recs into same area? (and since we can't, that is another reason we wanted to use separate workspaces and pass our respective UIs back and forth and finally into the shared "Library" area.)
Well, thank for reading through this and hopefully it makes sense.

Answer 1

OK Scott, let me try to clarify here:
Regardless of what reasons I have, my immediate goal is to sucessfully Export the UI Defaults from Schema A and Workspace A and Import into Schema B and Workspace B.
So, logging in as Schema A into Workspace A, I go to my app, then Export/Import then "Export User Interface Defaults". There is only one schema available to choose from in the "Schema" dropdown select list. I export the UI and save it to a file.
Next I logout and then login as Schema B into Workspace B. I go to Shared Components UI Defaults and display my tables. Most of these tables (about 30 of them) have the same exact name as the tables used by the other schema. UI Defaults do not exist.
I choose "Import" in the Tasks list, File Type "User Interface Defaults" and pick file I just exported. File is successfully Imported. Now I'm on screen for installing the UI Defaults. When I try to Import the UI it brings me to "Confirm Replace UI Defaults" and lists the OLD workspace schema (not the new one I expected)as being removed and replaced. I push ahead, tell it to do the replace and get the "You do not have access to the schema that you are importing". So I guess I'm doing something wrong.