on 2007 Jul 11 9:52 PM
Hello All
We have a case where we would like to move a selected set of materials from repository 1 to another repository 2 and still maintain the Key Mapping information that those materials have from the original Import into repository.
Any suggestion?
all help greatly appreciated
C
C,
Load the repository1 in Console and log into Data Manager. Download (import) the materials (to be moved to repository2) into your local pc as an excel file. Unload the repository1 in Console and load repository2. Log into the Data Manager and export (upload) the excel sheet.
Hope it resolves your problem.
Thanks,
Satyanarayana.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Con,
did you consider using Syndicator and Import Manager (or MDSS and MDIS)?! You could create a Syndication map with target system equal to the one you want to keep the key mapping. This would syndicate the full record including the key mapping information. With manual syndication you could put the file directly in the import folder, automatic syndication would need a mechanism (maybe a simple batch job?!) copying the file from outbound to import folder.
BR Michael
Hi Con,
The migration works fine for Product category wise from one repository to other repository but the Remote system information is not updating properly - correct me if am wrong.
<u>Possible place of corrections :</u>
1. Make sure the second repository's Key mapping property made YES > can be found at console>Repository-->Key mapping
please feel free to revert to me if things are not working.
thanks
Alexander
P.S.Kindly reward the points if found problem solved.
Yes., That is correct.
Our bbjective is to take a category, lets say "Caustic Soda" and migrate it to a new repository.This category contains materials form multiple remote systems and we are looking for the most effective way to migrate and maintain then correct key mapping details.
Thanking you in advance
Con
Hi Con,
I just want to summarize if I understood you right: you have a category that has some products. You want to migrate both into a second repository. Migration of the category is working but the key mapping information is lost or incomplete?!
How do your products look like? Do they have multiple key mapping entries? The syndicator would be able to distribute multiple key mappings (you can add multiple target systems in the destination properties of your map). But Import Manager is currently able to import only one key mapping records for a single remote system during an import run. This would mean that you have to syndicate your products for each remote systems and you have to do the same amount of imports.
BR Michael
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.