Repository Migration with Sub Processes
I have a migrator map file to migrate data from V7 to V9.
(A) Since "true" sub-processes are implemented in V9 now (such that sub-process data is stored in its own table), is there a way to map the data which should be placed into this sub-process table while using the migrate assistant tool? The variables are no longer in the main process.
I believe we can change the v9TableName value, but how does it know what value to put into eFolderID in case? Do I create a second mapping value for the eFolderID mapping?
(B) I doubt there is a solution for this, but now that child BOs can be accessed easier now, I want data which used to be in the main process to be moved to the child process instead. Again, I believe I can change the v9TableName setting, but its eFolderID is actually different. Is there a way to get the data across? (I doubt I have much hope for this one, but its worth asking.)
I'm hoping I don't have to do my own data migration, but I suspect I may have to anyway. Any insight or suggestions would be greatly appreciated.
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 151 General Questions
- 148 Thrust Services
- 57 OpenText Hackathon
- 37 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 186 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 8 XM Fax
- Follow Categories