NetSuite Release Notes

Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.

See TIBCO Scribe® Online Connector For NetSuite for more information.

 

Version 4.1.1

New And Noteworthy

There are no new features in this release.

Closed Issues

74284 / 74314

Users were unable to update an existing NetSuite connection from user based authentication to token based authentication. To address this issue a new field was added to the NetSuite Connection dialog where you can specify the authentication type, either user based or token based. Existing NetSuite Connections will continue to work, however, if you edit a NetSuite Connection, you must specify the authentication type. (Case # 69612)

Known Issues

73702

Summary: Entities that support Delete operations now require a DeleteReason consisting of a DeleteReasonCode and DeleteReasonMemo. When configuring a Delete Block, you can add the DeleteReasonCode and DeleteReasonMemo values on the Matching Criteria tab. DeleteReasonMemo is not required, however, whether it is provided or not, the default DeleteReasonMemo, "This transaction was deleted by script or web service", is used.

Workaround: Add DeleteReasonMemo to the Matching Criteria tab with a value of blank. ("").

73486

Summary: In the previous NetSuite API version used by the Connector for NetSuite, Address was a string field associated with an entity such as Order or Invoice. In the NetSuite 2018.2 API used in this release of the Connector, Address is a separate entity. To the extent possible, TIBCO Scribe® has addressed this issue by creating two virtual fields billAddress and shipAddress for entities that have an associated address. These virtual fields allow your flows to continue to run without requiring any changes.

In most cases, NetSuite has converted the data in the Address fields to Address records for the Address entity. However, very old Addresses that have not been updated may not have been converted and will not be included in source data when running a TIBCO Cloud™ Integration - Connect app.

Workaround: If you are missing Addresses in your source data, log into NetSuite and update the missing Addresses to trigger the conversion. Then, run your TIBCO Cloud™ Integration - Connect app again.

57388

Summary: When using NetSuite as a source, if you use a Lookup Block with no Matching Criteria, all records are returned instead of being limited to the default maximum of two records. This can cause the Connect on-premise agent to exceed its maximum storage capability.

Workaround: Be sure to include Matching Criteria or remove the Lookup Block from your flow.

46288

Summary: If a query or a lookup runs for a long time, it blocks other apps with a NetSuite Connection from running. For example, if you have a lookup on email address and you have many NULL email addresses in a large source database, this could cause the lookup to run for a very long time and return more records than expected. (Case # 59262)

Workaround: Review your data to determine whether you can do a lookup or a query with a different field as a filter. Another option is to check for NULL and when NULL is detected, use a value that you know is not in the database for the Matching Criteria on the lookup. This will allow the flow to continue with the next record.

 

Version 4.0.1

Released January 16, 2018.

New And Noteworthy

• Implemented Token Based Authentication when connecting to NetSuite through TIBCO Cloud™ Integration - Connect. (71646)
• Added support for the Create operation on the InventoryItem entity. (51511)
• Added support for the 2018.2 NetSuite API. (72572)

Changes In Functionality

Delete Operations

Entities that support Delete operations now require a DeleteReason consisting of a DeleteReasonCode and DeleteReasonMemo. When configuring a Delete Block, add the DeleteReasonCode and DeleteReasonMemo values on the Matching Criteria tab. If DeleteReasonCode and DeleteReasonMemo are not configured, the Connector supplies the following default values:

• DeleteReasonCode — 1 which is the value for Other.
• DeleteReasonMemo - "This transaction was deleted by script or web service"

Fields Removed From Metadata

The 2018.2 NetSuite API does not support all of the fields supported by the prior API. If you have any flows that use these fields you must update the field mappings or your integrations will fail with an error similar to the following:

"Operation failed. Label: Create Estimate, Name: EstimateCreate2, Message: There was a problem setting Netsuite field: accountType_internalId.: Error in calling Operation Create"

Fields that are no longer supported are as follows:

• EntityGroup
  • calendarname
  • calendarStartTime
  • calendarEndTime
  • calendarDefaultView
  • calendarPeriod
• Estimate
  • accountType_internalId
  • accountType_externalId
  • accountType_recordRefName
• Invoice
  • accountType_internalId
  • accountType_externalId
  • accountType_recordType
  • accountType_recordRefName
• ItemFulfillment
  • accountType_internalId
  • accountType_externalId
  • accountType_recordType
  • accountType_recordRefName
• SalesOrder
  • accountType_internalId
  • accountType_externalId
  • accountType_recordType
  • accountType_recordRefName
• SalesOrderItems
  • accountType_internalId
  • accountType_externalId
  • accountType_recordType
  • accountType_recordRefName

Closed Issues

70133 / 70134 / 70885

When using the Amazon S3 Connector with a NetSuite Connection and retrieving metadata for Custom Entities, the NetSuite Connector did not retrieve field information. This caused an error when attempting to map fields because no fields were available. The message: "No mappable fields exist on the chosen entity." was displayed. (Case # 67287)

 

Version 3.2.1

Released December 11, 2018.

New And Noteworthy

A new field has been added to the NetSuite Connection dialog that allows you to configure an ApplicationId. It is extremely important that you configure this ApplicationId for all of your NetSuite Connections before our January 14, 2019 release, which implements the requirement for that field.

On January 14, 2019 we are implementing the change on the NetSuite Connector to require the ApplicationId. If you do not make this update to your NetSuite Connections before the January 14 2019 release, your apps will fail.

For additional details and instructions, follow the link below to the NetSuite Connection Requirements Update Knowledge Base article.

Closed Issues

There are no Closed Issues in this release.

 

Version 3.0.1

Released May 2, 2017.

New And Noteworthy

Includes support for the following:

• Update operation for the InventoryItem entity (12031, 36544 / Case # 78401)
• Update operation for the Invoice entity (38521 / Case # 56234)
• Hyperlink custom field (18295, 36544 / Case # 81950)
• Entities with more than 1000 fields (10504, 36544)

Closed Issues

36498

A validation error is now generated if you map a Null value to a field that is type Enum. (Case # 55616)

39843

SalesOrders, Invoices, and Estimates can now be created in a NetSuite instance that does not use InventoryItem. (Case # 78821)

When creating a SalesOrder, Invoice or Estimate in NetSuite, NetSuite requires at least one child record, such as InventoryItem. The TIBCO Cloud™ Integration - Connect Connector For NetSuite creates a fictitious InventoryItem in NetSuite to serve as the required child record on new SalesOrders, Invoices, and Estimates until true InventoryItem records are added. When a real InventoryItem is added, the ficticious one is removed. If you do not have the Inventory Plugin for NetSuite, the TIBCO Cloud™ Integration - Connect Connector for NetSuite creates a fictitious NonInventoryItem instead.

Metadata Mismatches

Metadata mismatches between NetSuite and cached metadata in TIBCO Cloud™ Integration - Connect behave as follows:

For a metadata mismatch where a Source field with a modified Display Name is mapped to a target field, the value of the source field is not inserted and no error is generated.

3758

For a metadata mismatch in Match Criteria, a record error is generated with a message similar to the following: Operation failed. Label: Update Customer, Name: CustomerUpdate, Message: At least one NetSuite operation filter criteria is invalid.

36158 / 36453

For a metadata mismatch in your Query filter parameters, such as a field name in the filter that does not match any field name in the metadata, the execution ends with a fatal error and following message is generated: At least one of the NetSuite query parameters is invalid. Open your map, validate all links and filters, and try again. (Case # 55667)

37584

For a metadata mismatch when NetSuite is the target, a record error is generated with a message similar to the following:

Operation failed.  Label: Update Customer, Name: CustomerUpdate, Message: There was a problem setting Netsuite field: [field name]

 

October 2015 Release

New And Noteworthy

• Added paging capability - Enables you to use paging logic. If a timeout occurs during processing, this paging logic enables you to return all the records processed prior to the timeout.
• Added page size configuration - Enables you to specify the number of results to return per page, or to use the Search Page Size configured in NetSuite.
• Bulk operations support - All parent entities support bulk operations. Some child entities also support these operations. See the entity descriptions for details.

Closed Issues

There are no Closed Issues in this release.

 

September 30, 2015 Release

New And Noteworthy

There were no new features in this release.

Closed Issues

Integrations were failing for existing connections, after upgrading to the latest version of the NetSuite connector, with the following error:

The given key was not present in the dictionary.

Before this release, the only resolution to this error was to recreate any connections that caused the error.

 

April 8, 2015 Release

New And Noteworthy

This release adds support for the following entities:

• Estimates/Quotes
• Sales Orders
• Invoices
• Item Fulfillment
• Item Groups and various item entities
• Custom records and special custom fields

Closed Issues

There are no Closed Issues in this release.

Related Topics

Release Notes And Known Issues