1. NetSuite CPQ
  2. Migrating to NetSuite CPQ SuiteApps
  3. Migration Process
  4. Installing the SuiteApp and Importing Bundle Data

Installing the SuiteApp and Importing Bundle Data

Important:

You can't use the NetSuite CPQ SuiteApps and their records during the import process.

After creating backup data and uninstalling the bundles, you can install the NetSuite CPQ SuiteApps from the SuiteApp Marketplace.

Because the features and options of the NetSuite CPQ Configurator bundle are split into several SuiteApps, install the NetSuite CPQ Manufacturing, Proposal Generator, and Ecommerce Integration (formerly known as Background Configurator) SuiteApps to import the corresponding data.

For more information about installing the SuiteApps, see Installing the NetSuite CPQ SuiteApps.

Note:

Installing the Ecommerce Integration SuiteApp (formerly known as Background Configurator) requires NetSuite assistance. Before installing this SuiteApp, contact NetSuite Customer Support.

After the installation, the migration process automatically imports the backup data into the corresponding SuiteApp.

You can verify the import progress for NetSuite CPQ Configurator and Guided Selling SuiteApps by clicking the Global Import button at:

Accessing the Import Log Files

If the import process fails or completes with issues, you can find more information in the log files. When filing the support case, include the log files.

The following table lists the import log files for each SuiteApp.

SuiteApp

File Name

NetSuite CPQ Configurator

_BACKUP:importRes_configurator.json

NetSuite CPQ Proposal Generator

_BACKUP:importRes_propgen.json

NetSuite CPQ Guided Selling

_BACKUP:importRes_gs.json

To access the log files:

  1. Go to Documents > Files > File Cabinet.

  2. Click the following folders:

    1. SuiteScripts

    2. CPQ

    3. ProjectsBackup

  3. Select one of the following folders:

    • Configurator

    • Proposal Generator

    • GS

  4. Select the Migration Data folder.

  5. Click Download next to the log file you need.

Fixing Possible Import Issues on NetSuite CPQ Configurator Records

When importing records, the NetSuite CPQ Configurator SuiteApp verifies that all product records are properly filled in. During this process, NetSuite CPQ Configurator may find missing or incorrect information, such as a CSV table without information about the column separator. If any information is incomplete or missing, the product becomes inactive and it isn't displayed to users.

You can view inactive products in the internal product list at CPQ > Configurator > Product Maintenance. Inactive products are marked with Yes under the Inactive column.

Edit an inactive product to view the complete list of issues and instructions about how to fix them.

Note:

If you enable a product without fixing the issues, the affected records may not work properly, or you may be unable to use the product. Until you fix the issues, users won't be able to edit associated configured items on existing transactions.

To fix import issues:

  1. On the product list, edit the deactivated product.

  2. In the popup window, click the first record link.

  3. Solve the issue by following the instructions provided in the popup window.

  4. Save the record.

  5. In the Primary Information section, click the product link to go back to the product.

  6. Repeat steps 1 - 5 until you resolve every issue in the popup window.

To enable the product after fixing the issues, clear the Inactive box on the product record and save it.

Working with Existing Configured Items on Transactions

After importing bundle data into the NetSuite CPQ Configurator SuiteApp, the configuration data on existing transactions continue to be available. To edit imported configured items on existing transactions, users can click the Edit Config button on the configured line item.

For imported configured items, the SuiteApp Configurator Data transaction line field (field ID: custcol_cpqc_item_col_config_data) will appear blank. When users edit an imported configured item and submit the edited configuration, the updated data will show in the Configurator Data field.

The Configurator Data field for the bundle has been renamed to Configurator Data B (field ID: custcol_scpq_item_col_config_data). This bundle field continue to be available on transactions with its data but it will be hidden.

Related Topics

General Notices