Troubleshooting and support

Troubleshooting techniques and self-help information help you identify and solve problems quickly. This topic provides potential solutions for issues you would have with the NetSuite connector.

Points to note when upgrading to NetSuite 2013_2 with WebSphere Cast Iron NetSuite Connector

In NetSuite 2013_1 and earlier versions, every custom field in NetSuite was identified with an internalId (unique) attribute.

NetSuite has made the following changes in version 2013_2 and later versions:
  • scriptId is the new internalId
  • a new internalId attribute has been introduced
These changes affect all orchestrations that use the Cast Iron NetSuite connector, with the internal ID for custom fields being populated. If you upgrade the connector endpoints to version 2013_2 or a later version, these orchestration will stop working because the internalId attribute would still point to the old value.

Symptom

Orchestrations using the Cast Iron NetSuite connector stop working if you upgrade the connector endpoints to version 2013_2 or later versions of NetSuite.

Solution:
  1. Open each project using the NetSuite connector in IBM WebSphere Cast Iron Studio 7001.
  2. Go to each NetSuite endpoint, click the 'Update Wsdl to 2014_1' button and follow the steps to update the WSDL attached to the project.
  3. For each activity in every orchestration using NetSuite connector, go to the Configure Tab of the activity and press the refresh button to update the NetSuite object with the latest schema.
  4. Go to Map Input and Map Output section to ensure that the right value is populated for the internal ID field for the object and\or its child objects.
  5. Thoroughly test the orchestrations in the project in development environment, before moving into production.
  6. Repeat these steps for every project using NetSuite connector.



Feedback | Notices


Timestamp icon Last updated: Wednesday, 15 June 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/Netsuite_Troubleshooting.html