SendSuite Live version 7.15.01 Release Notes (January 4, 2017)

SendSuite Live Release Notes for version 7.15.01 (January 4, 2017).
Products affected: SendSuite® Live


This section describes the major new features or enhancements that are included in this release.

Support for Microsoft SQL Server Shared Management Objects (SMO) 2016

SendSuite Live now supports the latest version of SQL Server Shared Management Objects (SMO). For installations where the version of SQL Server Tools installed on the IIS server is SQL 2008 R2 or above, the latest 2016 SMO – which is compatible with earlier versions of SQL Server – can be installed using the MSIs located in the Resources\SQL 2016 Management Objects folder. It is a prerequisite that the appropriate SQLSysClrTypes installer (also located within the Resources folder) is run prior to installation of the updated SMO.

When installed in a domain environment, it remains the case that it may be necessary to amend the SendSuite Live connection string in order to create datasources from different SQL servers.



This section includes items that have been raised via Support and escalated to Development for resolution within this release.

GlobalTranz. URL Updated and PalletCount Element Added

The URL for the GlobalTranz carrier has been corrected. In addition, the shipping and rating functions have been corrected by the addition of a PalletCount element in the Rate and Ship transactions. When rating and shipping with this carrier, this new element should be populated with a value, otherwise the default of 1 is used.

Generation 2 Address Book. Resolved Duplicate Bulk List Error

An issue has been corrected whereby a duplicate bulk list error message was shown when two users imported contacts to a bulk list with the same name.



This section includes items that have been raised during UAT and escalated to Development for resolution within this release.

PB Shipping API – USPS. Transaction Reports. Resolved Issue with Refunds Not Totalling Correctly

This issue has been resolved.



This section contains information about minor changes and corrections. It can include issues raised in previous releases that have been corrected.

Shipment Server Configuration. Improved Search Performance

The performance of searching within two administration screens (Carrier Permissions and Document Viewer) has been improved. This change has resulted in the following new database indexes being created:

  • Accounts Table: IX_Accounts_AccountNumber: Index on AccountNumber field.
  • Users Table: IX_Users_UserName: Index on UserName field.
  • Profiles Table: IX_Profiles_Description: Index of description column

In addition, this change means that the Carrier Permissions and Documents Viewer screens now perform "starts with" searches by default rather than the previous "contains" searching. This change is to ensure the database indexing is used for performance reasons. To perform a "contains" search, use a % symbol at the start of the search expression. However, this will be a slower search.

UPS API. Resolved Issue with Time In Transit

An issue has been corrected whereby the Time In Transit transaction for UPS API would return a weight error when using multiple packages.

UPS API. Resolved Issue with Insurance Calculation

An issue has been corrected whereby the value NaN was sent to the carrier if an empty Insurance/Value node was passed during a Ship request. Empty nodes are now considered to be zero during the calculation.

Fix Output Suppression when Caching is Enabled

An issue has been corrected whereby using the Suppress flag within an environment where caching was enabled would cause the suppression status to also become cached. As a result, subsequent transactions would collect the Suppress value from a previous transaction rather than re-evaluating it.

Updated WorkstationIdentifier and Log Encoding

Two changes have been made to the application:

  • The log viewer now shows all logs as utf-8 encoded. Previously requests and responses were utf-16 encoded.
  • Support has been improved for IPv6 addresses within the client request. Previously, the application would add an IPv6 address to the incoming request if this was appropriate. However, all IP addresses are now base 64 encoded within the xml node (WorkstationIdentifier), to handle IPv6 addresses. Ultimately, the value added can be stored in the Packages Cache table for use with multi-piece shipping. In this case, the value is always decoded before storage so will appear in the database as readable text.



This section lists all changes that have the potential to break legacy functionality. Please review the contents of this section before updating any project to understand the changes that are being made and any actions that you need to take prior to applying the patches.

Change: New indexes have been added to the Accounts, Users and Profiles tables (IX_Accounts_AccountNumber, IX_Users_UserName and IX_Profiles_Description respectively).

Action: Ensure that no index with the same name already exists in the database before you install this patch.



The following XML Schema changes are included in this release.

For Schema Name:

  • Rate Request
  • Ship Requests

Added the following:

  • PalletCount: Pallet count for the GlobalTranz carrier.

UPDATED: August 14, 2021