Test NetSuite Data Imports

You can test whether your connection will import NetSuite data into Bronto as expected.

About this task

A test attempts to import a single contact or order record using either the contact's email address or the order's order ID. You do not have to have test mode on to test an import and have the option to decide whether or not to save the test record in Bronto.

Procedure

  1. Go to Settings > Integrations > Connector.
  2. Locate the connector you want to work with and click its Edit link.
  3. Click Advanced.
  4. To test a contact import:
    1. In the Schedule Task section, select Test Contact Import from the Task list.
    2. Select the type of NetSuite contact from the Stage list.

      For more information about NetSuite contact types see the NetSuite help topic.

    3. Enter a NetSuite contact's email address in the Email Address box.
    4. Select Yes or No from the Import Into Bronto list.

      If you select Yes, the data is saved in Bronto as you test. If you select No, the data is not saved in Bronto.

    5. Click Execute.
  5. To test an order import:
    1. In the Schedule Task section, select Test Order Import from the Task list.
    2. Select the NetSuite order record type from the Type list.
    3. Enter the NetSuite order ID in the Order Internal ID box.
      You can find the internal ID in the URL when you view the record in NetSuite. For example:

      https://system.na1.netsuite.com/app/accounting/transactions/salesord.nl?id=32726&whence=

    4. Select Yes or No from the Import Into Bronto list.

      If you select Yes, the data is imported into Bronto as you test. If you select No, the data is not saved in Bronto.

    5. Click Execute.
  6. After the import completes, refresh the contents of Connecter Advanced page.
  7. Scroll to the Execution Results section and click View Results to view the detailed results of your import.
    You can also look up the contact in Bronto, if you chose to import to Bronto.
    Note: The Connector will only show results for one completed task at a time.
  8. Make any adjustments you need to in the Contact Import settings and repeat the process with another example contact until the data is consistent with what the client wants.
  9. Complete additional verification in NetSuite after you test imports.
    1. Look at the system notes and workflow history for the imported record back in NetSuite to make sure that there are not any additional changes made from other customer scripts/workflows in NetSuite.
      To find this information, view the transaction record. Click on the System Information tab. The System Notes should only include the Bronto-specific fields changed by the integration, and potentially other fields that change from a blank old value to a new, default New Value.
    2. If there are additional actions taken on the record after the scripts run by the Integrations user, this can indicate additional scripts or workflows being triggered by the changes you make. In these cases, your NetSuite Administrator should work to identify the exact workflow or script responsible and edit it to have more specific triggers.
    Note: Test imports of individual records are only a simulation of the impact the full sync process could have on the synced NetSuite records. Certain criteria that are only met under specific circumstances on records, such as scripts that run when a specific record attribute criteria are met might not be identified using individual test imports.