Commerce Server Catalog - To migrate the display name and variant ID: (3 Catalogs)

This is Interesting: Free IT Magazines  
Home > Archive > Commerce Server Catalog > July 2004 > To migrate the display name and variant ID: (3 Catalogs)





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author To migrate the display name and variant ID: (3 Catalogs)
Shane M Ryan

2004-07-09, 3:17 pm

Does anyone have some working examples of this? We have three catalogs in
one site, how does this XML format look? Three XML files, or all in one?





To migrate the display name and variant ID:

Note Using the display name and variant ID, Name is the property you
currently use to store product display names. You must use the property name
NewVariantCodeProperty for the new catalog variant identifying property.

Create an XML file named c:\propertynames.xml in the following format:

<?xml version="1.0"?>

<UpgradeInfo>

<Catalog name="Adventure Works Catalog" productDisplayNameProperty="Name"
variantIdProperty ="NewVariantCodeProperty"/>

</UpgradeInfo>

CatalogMigrationTool.exe -S "Retail" -N "c:\propertynames.xml"

a.. To migrate only the Name property to the DisplayName property
(excluding the variant identifying property):
Create an XML file named c:\propertynames.xml in the following format:

<?xml version="1.0" ?>

<UpgradeInfo>

<Catalog name="Adventure Works Catalog"
productDisplayNameProperty="Name" />

</UpgradeInfo>

CatalogMigrationTool.exe -S "sitename" -N "displaynamesfile.xml"


Vinayak Tadas[MSFT]

2004-07-09, 3:19 pm

You can represent all the three catalogs in the same xml file

<?xml version="1.0"?>
<UpgradeInfo>
<Catalog name="Catalog1" productDisplayNameProperty="Name"
variantIdProperty ="NewVariantCodeProperty"/>
<Catalog name="Catalog2" productDisplayNameProperty="Name"/>
<Catalog name="Catalog3" productDisplayNameProperty="Name"
variantIdProperty ="NewVariantCodeProperty"/>
</UpgradeInfo>

You should specify the variantIdProperty only if your catalog has the same
productid and variantid property.


--------------------
From: "Shane M Ryan" <shanemryanNOSPAM@hotmail.com>
Subject: To migrate the display name and variant ID: (3 Catalogs)
Date: Wed, 7 Jul 2004 22:51:19 -0500
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <eXy6m7JZEHA.3844@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.commerceserver.catalog
NNTP-Posting-Host: adsl-66-137-138-181.dsl.rcsntx.swbell.net 66.137.138.181
Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXS01.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.commerceserver.catalog:4795
X-Tomcat-NG: microsoft.public.commerceserver.catalog

Does anyone have some working examples of this? We have three catalogs in
one site, how does this XML format look? Three XML files, or all in one?





To migrate the display name and variant ID:

Note Using the display name and variant ID, Name is the property you
currently use to store product display names. You must use the property name
NewVariantCodeProperty for the new catalog variant identifying property.

Create an XML file named c:\propertynames.xml in the following format:

<?xml version="1.0"?>

<UpgradeInfo>

<Catalog name="Adventure Works Catalog" productDisplayNameProperty="Name"
variantIdProperty ="NewVariantCodeProperty"/>

</UpgradeInfo>

CatalogMigrationTool.exe -S "Retail" -N "c:\propertynames.xml"

a.. To migrate only the Name property to the DisplayName property
(excluding the variant identifying property):
Create an XML file named c:\propertynames.xml in the following format:

<?xml version="1.0" ?>

<UpgradeInfo>

<Catalog name="Adventure Works Catalog"
productDisplayNameProperty="Name" />

</UpgradeInfo>

CatalogMigrationTool.exe -S "sitename" -N "displaynamesfile.xml"




Thanks
Vinayak Tadas
Microsoft
http://blogs.msdn.com/vinayakt

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure! For more info visit http://www.microsoft.com/security. Please
reply to the newsgroups only. Thanks

Shane M Ryan

2004-07-09, 3:21 pm

Where do I find this parameter?

productDisplayNameProperty="Name"

what is name?






"Vinayak Tadas[MSFT]" <vtadas@online.microsoft.com> wrote in message
news:wv31%23gRZEHA.600@cpmsftngxa06.phx.gbl...
> You can represent all the three catalogs in the same xml file
>
> <?xml version="1.0"?>
> <UpgradeInfo>
> <Catalog name="Catalog1" productDisplayNameProperty="Name"
> variantIdProperty ="NewVariantCodeProperty"/>
> <Catalog name="Catalog2" productDisplayNameProperty="Name"/>
> <Catalog name="Catalog3" productDisplayNameProperty="Name"
> variantIdProperty ="NewVariantCodeProperty"/>
> </UpgradeInfo>
>
> You should specify the variantIdProperty only if your catalog has the same
> productid and variantid property.
>
>
> --------------------
> From: "Shane M Ryan" <shanemryanNOSPAM@hotmail.com>
> Subject: To migrate the display name and variant ID: (3 Catalogs)
> Date: Wed, 7 Jul 2004 22:51:19 -0500
> Lines: 42
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> Message-ID: <eXy6m7JZEHA.3844@TK2MSFTNGP10.phx.gbl>
> Newsgroups: microsoft.public.commerceserver.catalog
> NNTP-Posting-Host: adsl-66-137-138-181.dsl.rcsntx.swbell.net

66.137.138.181
> Path:
>

cpmsftngxa06.phx.gbl!TK2MSFTNGXS01.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
> 8.phx.gbl!TK2MSFTNGP10.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.commerceserver.catalog:4795
> X-Tomcat-NG: microsoft.public.commerceserver.catalog
>
> Does anyone have some working examples of this? We have three catalogs in
> one site, how does this XML format look? Three XML files, or all in one?
>
>
>
>
>
> To migrate the display name and variant ID:
>
> Note Using the display name and variant ID, Name is the property you
> currently use to store product display names. You must use the property

name
> NewVariantCodeProperty for the new catalog variant identifying property.
>
> Create an XML file named c:\propertynames.xml in the following format:
>
> <?xml version="1.0"?>
>
> <UpgradeInfo>
>
> <Catalog name="Adventure Works Catalog" productDisplayNameProperty="Name"
> variantIdProperty ="NewVariantCodeProperty"/>
>
> </UpgradeInfo>
>
> CatalogMigrationTool.exe -S "Retail" -N "c:\propertynames.xml"
>
> a.. To migrate only the Name property to the DisplayName property
> (excluding the variant identifying property):
> Create an XML file named c:\propertynames.xml in the following format:
>
> <?xml version="1.0" ?>
>
> <UpgradeInfo>
>
> <Catalog name="Adventure Works Catalog"
> productDisplayNameProperty="Name" />
>
> </UpgradeInfo>
>
> CatalogMigrationTool.exe -S "sitename" -N "displaynamesfile.xml"
>
>
>
>
> Thanks
> Vinayak Tadas
> Microsoft
> http://blogs.msdn.com/vinayakt
>
> This posting is provided "AS IS" with no warranties, and confers no

rights.
> You assume all risk for your use. © 2002 Microsoft Corporation. All rights
> reserved.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> Get Secure! For more info visit http://www.microsoft.com/security.

Please
> reply to the newsgroups only. Thanks
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com