12 SALESFORCE

============================================================================== Magnitude Simba Salesforce ODBC Data Connector Release Notes ==============================================================================

The release notes provide details of enhancements, features, known issues, and workflow changes in Simba Salesforce ODBC Connector 3.0.0, as well as the version history.

3.0.0 ========================================================================

Released 2023-04-13

Enhancements & New Features

  • [SF-903] Updated third-party libraries

    The connector now uses the following third-party libraries:

    • Expat 2.5.0 (previously 2.4.6)
    • ICU 71.1.x (previously 58.3.x)
    • libcURL 7.88.1 (previously 7.84)
    • OpenSSL 3.0.0 (previously 1.1.1)
    • zlib 1.2.13 (previously 1.2.11)

  • [SF-920] Updated platform support

    The connector now supports the following platform versions:

    • Windows 11
    • Windows server 2022
    • macOS 11.0 ARM
    • Debian 10 and 11
    • Red Hat Enterprise Linux (RHEL) 8 and 9
    • SUSE Linux Enterprise Server (SLES) 15
    • Ubuntu 20.04 and 22.04

    For a list of supported platform versions, see the Installation and Configuration Guide.

  • [SF-890] Support for UseDefaultSystemProxy

    The connector can now be configured to read the proxy settings from the default system configuration. To do this, enable the UseDefaultSystemProxy property to 1. For more information, see the Installation and Configuration Guide.

Known Issues The following are known issues that you may encounter due to limitations in the data source, the connector, or an application.

  • Text area fields return string data “as is” from the REST API, possibly returning carriage-return line-feed sequences instead of
    line-feeds only, as was usual for the SOAP API.

  • There are rounding discrepancies between SOAP, REST and Bulk API when using the SOQL CONVERTCURRENCY scalar function.

  • The CONVERTCURRENCY, DISTANCE, and FORMAT functions are not supported in filters.

    These SOQL functions and their aliases cannot be used in filters. Only fields can be used in filters.

  • The following SQL features are not supported by the connector:

    • Typeof
    • Offset
    • With

  • Binary data types are not supported for INSERT, UPDATE, and DELETE statements.

  • Support for the Encrypted TextArea custom field type is limited.

    The connector retrieves the field as a string of asterisks (for example, “***“), which may cause filtering to be incorrect.

  • Query processing is not optimal when GROUP BY returns large result sets.

    Normally, when a result set exceeds 2000 rows, the connector will use the queryMore() call and a server-side cursor to retrieve additional rows in 1000-row chunks. Doing so allows the query to be processed efficiently. However, if the query contains a GROUP BY clause, then queryMore() cannot be used. In this case, you must change the filtering conditions to query data in smaller chunks.

  • SQL string operators are case-sensitive.

    Although Salesforce uses case-insensitive matching for string operators such as “=” and “LIKE”, the connector processes SQL string operators in a case-sensitive manner.

  • Restrictions in queries may not be enforced during the prepare stage.

    A query may succeed during the prepare stage even if it violates one of the following:

    • Restrictions on using ToLabel() in the filter clause.
    • Restrictions on using fields in the HAVING clause.
    • Restrictions on the operations that can be performed for specific data types. For example, ORDER BY is not supported for the following data types:
      • Multi-select picklist
      • Rich text area
      • Long text area
      • Encrypted The query fails when it is executed.

  • If unixODBC 2.3.1 is used, the connector terminates unexpectedly when calling SQLSetConnectAttr with the SQL_ATTR_ODBC_CURSORS attribute. The ODBC specification does not recommend using this library.

Workflow Changes =============================================================

The following changes may disrupt established workflows for the connector.

3.0.0 ————————————————————————

  • [SF-920] Removed support for OS platforms

    Beginning with this release, the connector no longer supports the following OS platforms:

    • Windows 8.1 and 7 SP1
    • Windows Server 2008 R2 SP1
    • macOS 10.13 and 10.14
    • Debian 8 and 9
    • Red Hat Enterprise Linux (RHEL) 6
    • SUSE Linux Enterprise Server (SLES) 11
    • Ubuntu 16.04 and 18.04

    For a list of supported OS versions, see the Installation and Configuration Guide.

2.2.22 ——————————————————————

  • Removed support for Ubuntu 14.04

    Beginning with this release, the connector no longer supports Ubuntu 14.04. For a list of supported Linux versions, see the Installation and Configuration Guide.

2.2.21 ———————————————————————–

  • [SF-798] Removed support for earlier versions of Windows

    Beginning with this release, the connector no longer supports the following versions of Windows:

    • Windows 7
    • Windows Server 2008
    • Windows Server 2008r2

    For a list of supported Windows versions, see the Installation and Configuration Guide.

  • [SF-797] Removed support for macOS 10.12 and earlier

    Beginning with this release, the connector no longer supports the following versions of macOS:

    • macOS 10.12
    • macOS 10.11
    • macOS 10.10
    • macOS 10.9

    For a list of supported macOS versions, see the Installation and Configuration Guide.

2.2.20 ———————————————————————–

  • [SF-799] Removed support for CentOS 6

    Beginning with this release, the connector no longer supports CentOS 6. For a list of supported Linux versions, see the Installation and Configuration Guide.

  • [SF-796] Removed support for Visual Studio 2013

    Beginning with this release, the connector no longer supports Visual Studio

    1. For a list of supported Visual Studio versions, see the Installation and Configuration Guide.

2.2.12 ———————————————————————–

  • Rollback of 2.2.11

    Due to unforeseen issues with the 2.2.11 release, all features and resolved issues included in that release have been rolled back as of this release. For information on the features and resolved issues that have been rolled back, see the 2.2.11 section in the Version History.

2.2.1 ————————————————————————

  • Minimum TLS Version

    Beginning with this release, the driver requires a minimum version of TLS for encrypting the data store connection. By default, the driver requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to data stores that use a TLS version earlier than 1.2.

    To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, see the Installation and Configuration Guide.

Version History ==============================================================

2.2.22 ———————————————————————–

Released 2022-03-29

Enhancements & New Features

  • [SF-863] Configure OAuth 2.0 properties in DSN configuration dialog

    On Windows, the DSN configuration dialog now includes fields for configuring OAuth 2.0 connection properties. For more information, see the Installation and Configuration Guide.

  • [SF-866] Support for SELECT FIELDS

    The connector now supports the SELECT FIELDS statement. For more information, see the Salesforce SOQL and SOSL Reference Guide: https://developer.salesforce.com/docs/atlas.en-us.230.0.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_fields.htm

  • [SF-869] Support for GCC 5.5

    On Linux, the connector is now statically linked to GCC 5.5.

  • [SF-877] Updated libcURL library

    The connector now uses libcURL library version 7.78.0 Previously, the connector used libcURL 7.74.0.

Resolved Issues The following issue has been resolved in Simba Salesforce ODBC Connector 2.2.22.

  • [SF-875] In some cases, when locating the field search position of a value, the connecter terminates unexpectedly. For example, when the connector attempts to locate a value in a table schema.

2.2.21 ———————————————————————–

Released 2021-09-23

Enhancements & New Features

  • [SF-858] Support for Windows Server 2019

    The connector now supports Windows Server 2019. For a list of supported Windows versions, see the Installation and Configuration Guide.

Resolved Issues The following issue has been resolved in Simba Salesforce ODBC Connector 2.2.21.

  • [SF-861] When using SOQL and the specified condition is set to Japanese, the connector does not retrieve data.

2.2.20 ———————————————————————–

Released 2021-06-29

Enhancements & New Features

  • [SF-854] Upgrade to libcURL 7.74

    The connector now uses libcURL library version 7.74. Previously, the connector used libcURL 7.66.0.

Resolved Issues The following issue has been resolved in Simba Salesforce ODBC Connector 2.2.20.

  • [SF-830] When comparing HTTP headers, the connector treated the headers as case-sensitive.

2.2.19 ———————————————————————–

Released 2020-10-30

Enhancements & New Features

  • [SF-814] Support for OAuth 2.0 authentication

    The driver now supports OAuth 2.0 authentication. For more information, see the Installation and Configuration Guide.

  • [SF-829] Updated logging configurations

    The logging configurations for a particular connection can now be passed in via the connection string or DSN. For more information, see the Installation and Configuration Guide.

Resolved Issues The following issues have been resolved in Simba Salesforce ODBC Driver 2.2.19.

  • [SF-830] If a call returns an invalid response, the driver does not retry URL retrieval.

  • [SF-831] On Windows, when the trust store fails through libcURL, the driver does not retry the connection.

  • [SF-835] Queries longer than 10000 characters result in the driver returning a “Conversion from string to number failed with value ’’” error.

  • [SF-837] When Date or Time data is invalid, the driver does not return an error.

    This issue has been resolved. The driver now prompts the user to provide the correct information.

2.2.18 ———————————————————————–

Released 2020-09-25

Resolved Issues The following issue has been resolved in Simba Salesforce ODBC Driver 2.2.18.

  • [SF-832] In some cases, the driver cannot be loaded.

2.2.17 ———————————————————————–

Released 2020-08-19

Resolved Issues The following issues have been resolved in Simba Salesforce ODBC Driver 2.2.17.

  • [SF-811] For string data types, when returning from SQLColumns(), the driver returns column sizes that are larger than the actual character size.

  • [SF-815] In some cases, when calling scalar functions on string data, the driver returns the following error: “Incompatible collations found”.

  • [SF-816] In some cases, when querying on big object, the driver returns the following error: “Conversion from string to unsigned number failed with value ‘-1’”.

2.2.16 ———————————————————————–

Released 2020-04-28

Enhancements & New Features

  • [SF-802] Support for chunked data fetching in JunctionIDList columns

    You can now fetch data in chunks from JunctionIDList columns. You can specify the chunk size with the InitialJunctionIdListFetchSize and MaxJunctionIdListFetchRetries configuration properties. For more information, see the Installation and Configuration Guide.

Resolved Issues The following issue has been resolved in Simba Salesforce ODBC Driver 2.2.16.

  • In some cases, an object that contains a JunctionIdList does not return all of the data.

    This issue has been resolved. For more information, see [SF-802] in Enhancements & New Features.

2.2.15 ———————————————————————–

Released 2020-02-21

Enhancements & New Features

  • [SF-794] Upgraded Expat library

    The driver now uses version 2.2.9 of the Expat library. Previously the driver used version 2.2.0.

Resolved Issues The following issue has been resolved in Simba Salesforce ODBC Driver 2.2.15.

  • [SF-792] In some cases, when the driver casts a timestamp value to a DATE column, the driver terminates unexpectedly.

2.2.14 ———————————————————————–

Released 2020-01-22

Enhancements & New Features

  • [SF-787] Configurable Salesforce API version

    You can now specify the Salesforce API version that the driver uses for the connection. To do this, set the new ApiVersion connection property. For more information, see the Installation and Configuration Guide.

Resolved Issues The following issues have been resolved in Simba Salesforce ODBC Driver 2.2.14.

  • [SF-639] In some cases, queries that involve null values can cause the driver to return columns in an incorrect order.

  • [SF-680] In some cases, when executing a query that contains an aggregate function or a GROUP BY clause, the driver terminates unexpectedly.

  • [SF-786] When retrieving binary data that exceeds 2000 rows, the driver returns an error.

2.2.12 ———————————————————————–

Released 2019-11-06

  • Due to unforeseen issues with the 2.2.11 release, all features and resolved issues included in that release have been rolled back as of this release. For information on the features and resolved issues that have been rolled back, see the 2.2.11 section in the Version History.

Enhancements & New Features

  • [SF-782] Upgrade to OpenSSL 1.1.1d

    The driver now uses OpenSSL 1.1.1d for encryption of data. Previously the driver used OpenSSL 1.1.0j.

  • [SF-785] Upgrade to libcURL 7.66.0

    The driver now uses libcURL library version 7.66.0.

Resolved Issues The following issue was resolved in Simba Salesforce ODBC Driver 2.2.12.

  • [CROSS-75] The driver terminates unexpectedly when both of the following occur:
    • Multiple database drivers are loaded to the same process.
    • One driver unloads and calls ICU’s u_cleanup() function, while another driver continues to run and tries to access the memory space that has been cleaned up.

==============================================================================

Installation and Configuration Guide