This content has been marked as final. Show 7 replies
Does it work if you select all the artifacts for the planning application?
I selected all on the export. I haven't tried selecting all on the import. Would that really work? We always had to do this in steps before. Atleast with EPMA apps. I'll try now.
OK. I had to move to my cloud instance on Amazon. It's the one from John Booth. Anyways, I copied the folder into the 'import_export' directory and when I click on 'File System' in Shared Services, I don't see my folder. Thus not sure how I can proceed.....
OK. I ran a sample extract so it would point me to correct 'import_export' directory. I created a sample app. Should I use that one and select it during import process?
OK. More details now that I have been experimenting a bit.
1 - If I create a data source named exactly how the data source is named on the source system, it will migrate perfectly even if the application doesn't exist yet. It will actually create it like it says it will.
2 - If I create a data source and name it something different than the data source name on source system, I can migrate the Configuration->Properties->Application Definition and Configuration->Properties->Application Settings successfully. However when I try and then migrate the 'Global Artifacts' and 'Plan Types' I get tons of errors.
Example Error: Error in migrating artifact, "/Plan Type/Capex/Rule files/Depr.rul". Database Capex does not exist
Prior to attempting #2 above I manually create a Planning App and then during migration I select that application to apply import to. Not sure what's going on or why.
I think, we need to have same database names in both source & destination applications y b'coz in rules those internally associated with plan type names.
Data Source names have to be same, but that makes no sense. Anyways, got it to work that way. Not sure why it doesn't work the other way.