NetSuite (CData) 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 (CData) for more information.
Version 1.3.1
Released February 17, 2021.
New And Noteworthy
- Updated the ADO.NET data provider to version 1.2.0.0.
- Updated the NetSuite CData Driver to version 20.0.7598.0.
- Added support for Token-Based Authentication. (SCNETSC-181)
- Added support for NetSuite Restlets. (SCNETSC-232)
Changes In Functionality
- CData logging is no longer enabled by default. To enable logging, set the Verbosity parameter to Verbosity=1 in the Additional Parameters field on the Connection dialog. Note that Verbosity can be set to any level 1 through 5 to enable logging, however, the higher the level the more information is logged. (SCNETSC-132, SCNETSC-107)
- MaxLogFileSize and MaxLogFileCount parameters are overridden by the Connector. MaxLogFileSize is set to 10MB and MaxLogFileCount is set to 5 files. When the maximum number of CData log files is reached, the oldest file is overwritten. (SCNETSC-132, SCNETSC-107)
- For existing Connections, if the new Api Version field on the Connection dialog is empty, the Connector defaults to Version 2017.1 of the NetSuite API. When configuring a new Connection, you are required to select a version. You may need to modify existing NetSuite Connections to specify the version of the API you want to use. (SCNETSC-175, SCNETSC-181)
- The authentication type and API version configured in the Connection dialog affect whether or not the Connector can access the maximum number of concurrent sessions configured for a NetSuite account as follows:
- User Credentials — Can only be used for a maximum of one concurrent session. For this authentication type, NetSuite does not support using the maximumconcurrentsessions connection property to increase the number of concurrent sessions.
- Token Based Authentication —
- If you have configured NetSuite API version 2020.1 or higher in the Connection dialog, the Connector uses the Concurrency Limit from the NetSuite Integration associated with the Connection.
- If you have configured a NetSuite API version lower than 2020.1 in the Connection dialog, the Connector cannot determine the Concurrency Limit from the NetSuite Integration associated with the Connection. A default value of three is used. You can override the default by setting a value for the maximumconcurrentsessions connection property in the Additional Parameters field on the Connection dialog.
Closed Issues
SCNETSC-444
Metadata returned by the CData driver was missing items. (Case # 01898499, 01898472)
SCNETSC-443
The CreateSavedSearchSchema stored procedure did not accept some SearchType parameters, such as, AssemblyItem and generated errors similar to the following: Could not execute the specified command: The operation CreateSavedSearchSchema.rsb expects one of the following as a value for the attribute SearchType'. (Case # 01898499, 01898472)
SCNETSC-442
Querying custom fields with spaces in the field name generated exceptions when the app ran. (Case # 01898499, 01898472)
SCNETSC-359
Item entity InternalID field values were returned as NULL instead of the actual value. (Case # 01883136)
SCNETSC-170
Adding an item to SalesOrder_itemList generated a ReplaceAll validation error. (Case # 01864647)
SCNETSC-159
When updating a custom item list field for the CashSale_ItemList entity, an "Invalid attribute name" error was generated. (Case # 01843257)
SCNETSC-111 / SCNETSC-99 / SCNETSC-2
Flows that processed large numbers of records and ran over a long period of time sometimes generated intermittent "Object reference not set to an instance of an object" errors. When the records with errors were reprocessed, they did not generate any further errors. (Case # 01760802)
SCNETSC-107 / 75351
Log files for the Connector were enabled by default. The size of each log file was limited, but the number of log files was not limited, causing the Agent Logs folder to grow without bounds. (Case # 01760802)
SCNETSC-103
Using the NExIL Extended accounting Localization for NetSuite customization caused Malformed SQL Statement errors when querying NetSuite. (Case # 01798178)
Known Issues
SCNETSC-469
Summary: Fetching NetSuite data using Restlets fails to create a schema .RSD file and no fields are returned. An error similar to the following is generated:
"Message: Fetch properties and relationships 1st retry error:
Exception Type : InvalidCastException
Message : Unable to cast object of type 'System.Int32' to type 'System.String'. "
Workaround: Contact Support for assistance.
SCNETSC-468
Summary: Token-Based Authentication is not working for NetSuite Sandbox Environments when the Account ID contains an underscore (_), such as 123456_SB1, because the NetSuite Suitetalk URLused for the authorization/connection, contains a dash "https://123456-sb1.suitetalk.api.netsuite.com/services/NetSuitePort_2020_1
Workaround: In the Connection Configuration dialog, select User Credentials as your Authentication. Fill in the required fields for that Authentication type. In the Additional Parameters field, include the parameters for Token-Based Authentication separated by semicolons (;).
Example:
OAUTHACCESSTOKEN=XXX; OAUTHACCESSTOKENSECRET=XXX;
OAUTHCLIENTID=XXX; OAUTHCLIENTSECRET=XXX
SCNETSC-150
Summary: Performance is very slow when using the OR operator in a query filter.
Workaround: None.
70338 / SCNETSC-145
Summary: When querying the Invoice_ItemList entity and using Net Change, only a single Invoice and a single line item are returned even though more records exist.(Case # 67209, 01727334)
Workaround: Disable the filter on the Net Change tab.
SCNETSC-133
Summary: Attempting to create records for an entity that is type Custom List fails and the records are not added.
Workaround: None.
SCNETSC-131
Summary: Running a query and filtering on a field that contains a period (.) in the name generates errors similar to the following:
ERROR: Exception Type : NetSuiteException
Message : [500] Could not execute the specified command: No table found with the alias 'Dean'.
Workaround: None: When creating custom fields in NetSuite, do not use a period (.) or other special characters in the name.
SCNETSC-130
Summary: Creating records for an entity with a name that contains an ampersand (&) generates errors similar to the following:
Operation failed. Label: Create DeanAmpersand, Name: DeanAmpersandCreate, Message: [500] Could not execute the specified command: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 85; The entity name must immediately follow the '&' in the entity reference.
Workaround: None. When creating a custom entity in NetSuite, do not use the ampersand (&) or other special characters in the name.
64451 / SCNETSC-101
Summary: When mapping fields to NetSuite as a target, required fields are not displayed in bold nor are they noted as required in the field descriptions.
Workaround: None.
64012 / SCNETSC-102
Summary: When using Native Query to retrieve records from NetSuite, if the SQL statement has a contains operator before an OR, only the records that match the filter after the OR are returned. For example, if the following SQL statement is used, only the records that match the IsInactive=true filter are returned.
Select * from Customer where CompanyName contains 'Smith%' OR IsInactive=true
Workaround: Use a different operator before the OR, such as =, or use the regular Query Block instead of the Native Query Block.
Summary: In some cases, when using a Connect cloud agent with logging enabled, the first log file is created successfully but only a small amount of data is added.
Workaround: If you need logging to diagnose an issue, install an Connect on-premise agent and use that agent to run the app.
Version 1.0.0
Released May 14, 2018.
New And Noteworthy
The Connector for NetSuite (CData) supports the following:
- Query, Native Query, Create, Update, and Delete operations for many NetSuite entities.
- Net Change to query for new and updated records based on any date or timespan field.
Closed Issues
There are no Closed Issues in this release.