What are the steps to be followed to compare the Node ID between Test and Production while configuring Guided Buying?

If the Catalog Hierarchy Node ID in your TO-BE-PRODGB.JSON file is different from what you want to use in your Production GB site, then follow the steps below to find and replace the Node ID:

4. 1. On the dashboard, click Manage -> Core Administration.
   2. Choose Catalog Manager Hierarchy Editor.
   3. Click File and then choose Export Hierarchy from the drop down. You have the option to open or save the catalog hierarchy XML file.
   4. Open the XML file in a text-editing program, such as Notepad++.
   5. Find the ProductCategoryBranch or ProductCategoryLeaf that corresponds to the category you want to associate with a landing page tile.

Example:

You are configuring a landing page tile for toner for printers and copiers and you want all the available toner products to show up when users access this tile. After downloading the catalog hierarchy file, search the file for "toner" and find the following ProductCategoryLeaf:

<ProductCategoryLeaf nodeID="NI.146.1146072102234">

<Description xml:lang="en-US">Toner</Description>

<Description xml:lang="x-ariba-I18N">@ariba.catalog.hierarchy/Toner</ Description> <Description xml:lang="en-US">Toner</Description> <ProductCategoryConditions> <IsIn> <Field>ClassificationCode.unspsc</Field> <Literal>44103103</Literal> </IsIn> </ProductCategoryConditions> </ProductCategoryLeaf>

To show all the right products when users access the toner tile, you need to map the tile to node ID NI. 146.1146072102234. Make note of all the node IDs that you plan to use to configure your landing pages.

Guided Buying > Guided Buying Administration > Policies