Release Notes Simba

Release Notes
Simba Salesforce ODBC Driver with SQL Connector

1.1.28
The release notes provide details of enhancements and features in Simba Salesforce ODBC Driver
with SQL Connector 1.1.28, as well as the version history.
Resolved Issues
The following issues have been resolved in Simba Salesforce ODBC Driver with SQL Connector
1.1.28.
When using the driver in Crystal Reports 2008, numbers are mapped to a string data type
instead of a numeric data type
This issue has been resolved.
Known Issues
The following are known issues that you may encounter due to limitations in the data source, the
driver, or an application.
Binary data types are not supported for INSERT, UPDATE, and DELETE statements
You cannot use INSERT, UPDATE, and DELETE statements on Binary data.
Version History
Version 1.1.27
Resolved Issues
The following issues were resolved in Simba Salesforce ODBC Driver with SQL Connector 1.1.27.
When using the Analytic API to execute reports, the driver does not interpret Unicode procedure
column names correctly
www.simba.com 1
Simba Salesforce ODBC Driver with SQL Connector 1.1.28 Release Notes
Version 1.1.26
Enhancements & New Features
The following are highlights of the new features and functionalities that were added to Simba
Salesforce ODBC Driver with SQL Connector 1.1.26.
Salesforce Professional Edition now supported
The driver now supports Salesforce Professional Edition as a certified partner application
for Salesforce.com.
Resolved Issues
In some cases, the driver does not interpret Unicode procedure names and procedure column
names correctly
This issue has been resolved. The driver now decodes procedure and procedure column
names from UTF-8 correctly.
Driver fails to parse SOQL queries containing datetime literals with fractional seconds
When testing a connection through the DSN configuration dialog box on Windows, the driver
logs the password
Driver fetches data incorrectly for some SOQL queries containing aggregate functions
Version 1.1.25
Salesforce API version 34 now supported
The driver now uses Salesforce API version 34. Previously, the driver used version 32 of the
API.
www.simba.com 2
Aliases now supported
The driver now supports the use of aliases in SOQL queries.
Version 1.1.24
Updated dialog box names in the Windows driver
The Salesforce Configuration dialog box is now called the Salesforce ODBC Driver DSN
Setup dialog box. Also, the Salesforce ODBC Connection dialog box is now called the
Salesforce ODBC Driver Connection dialog box.
Version 1.1.23
Updated the default location of the simba.salesforceodbc.ini configuration file
By default, the simba.salesforceodbc.ini configuration file is now located in the lib

directory corresponding to the bitness of the driver. For example, the configuration file
for the 64-bit driver on Linux is located in /opt/simba/salesforceodbc/lib/64
Updated driver configuration process
The updated default behavior of the driver is to read the simba.salesforceodbc.ini file
from its new default location in the lib directory. You no longer need to copy the
simba.salesforceodbc.ini configuration file into the home directory.
SIMBAINI environment variable renamed to SIMBASALESFORCEINI
The environment variable for locating the simba.salesforceodbc.ini configuration file has
been renamed from SIMBAINI to SIMBASALESFORCEINI. The default value of
SIMBASALESFORCEINI is the default installation location of the simba.salesforceodbc.ini
file.
Implemented configuration option for specifying a security token
Before, you would provide a security token by appending it to the end of your password.
The Windows driver now provides a "Security Token" field in the DSN Setup dialog box,
www.simba.com 3
and all versions of the driver now support a SecurityToken key. Use these new options to
specify a security token instead of appending it to your password.
Note: You can configure the Windows driver to save your security token in the DSN by
enabling the new "Save Security Token" option in the DSN Setup dialog box.
Updated "Test" functionality in the Windows driver
When you click the "Test" button in the DSN Setup dialog box, the driver now checks the
license file and reports if it has expired, and also reports some additional driver details.
Renamed "Strip catalog name" configuration option
The "Strip catalog name" option is now called "Strip catalog name from filter arguments".
Updated "Proxy Port" field
In the Windows driver, the "Proxy Port" field in the DSN Setup dialog box no longer
accepts non-numeric characters.
Updated handling of Sandbox URLs
The driver can now remove trailing slashes (/) when validating Sandbox URLs.
Resolved Issues
In some cases, queries involving the User table are not executed correctly
This issue has been resolved. You no longer need to quote the User table in order to use it
in a query. This change resolves issues that occurred previously when using the driver with
Microsoft Access or Microsoft Query.
Version 1.1.22
Updated to Salesforce API version 32
The driver now uses Salesforce API version 32.
Support added for passing down aggregations
To improve driver performance, aggregations are now passed to Salesforce when possible.
www.simba.com 4
Updated handling of the Currency and Percent data types
The driver now returns Currency and Percent data from Salesforce as SQL_NUMERIC.
Before, Currency and Percent data was returned as SQL_DOUBLE.
Implemented configuration option for returning data as SQL_WVARCHAR instead of

SQL_VARCHAR
You can now configure the driver to return data as SQL_WVARCHAR instead of
SQL_VARCHAR by enabling the "Use SQL_WVARCHAR instead of SQL_VARCHAR" option
(set the UseWVarChar key to 1).
Implemented configuration option for returning result set columns as SQL_NUMERIC instead of
SQL_DOUBLE
You can now configure the driver to return result set columns as SQL_NUMERIC instead
of SQL_DOUBLE by enabling the "Use SQL_NUMERIC for result set columns of type
SQL_DOUBLE" option (set the UseNumeric key to 1).
Updated Logging Options dialog box
The "Log Namespace" field has been removed from the Logging Options dialog box. Also,
you can now browse for a directory to use as the log path instead of typing the file path
into the "Log path" field.
Implemented configuration option for specifying the domain in a Salesforce user name
Salesforce user names consist of a user ID and a domain (for example,

myuser@myorganization.com). Some ODBC applications do not allow the at sign (@) to
be part of the user name. As a workaround, you can now use the UIDDomain key to
specify the domain separately from the user ID.
Resolved Issues
Driver incorrectly reports the length of Address data as 0
This issue has been resolved. The driver now reports the correct length for Address data
from Salesforce.
Driver incorrectly reports binary length instead of character length for String data
This issue has been resolved. The driver now correctly reports the length of String data
from Salesforce.
www.simba.com 5
Driver incorrectly reports keys as non-unique for SQLStatistics
This issue has been resolved. SQLStatistics now reports keys as unique.
Incorrect default setting for the "Enable report metadata optimization" option
This issue has been resolved. Before, the "Enable report metadata optimization" option
was enabled by default (the MetadataLevel key was set to 1 or LIGHT). It is now disabled
by default (set to 0 or FULL).
Version 1.1.21
Added logging for connection attributes
The driver now logs the connection attribute key-value pairs when driver logging is
enabled.
Resolved Issues
Description of "Strip Catalog Names" in the documentation is inaccurate
This issue has been resolved. The install guide has been revised to provide a more accurate
description of the "Strip Catalog Names" feature.
Version 1.1.20
Implemented new "Strip Catalog Names" configuration option
You can now enable the driver to remove catalog names from the TableName parameter
in the SQLTables ODBC API function call. Some applications include catalog names in the
TableName parameter, and the catalog names may need to be removed. To configure this
option, use the "Strip Catalog Names" check box in the Windows driver or the
StripCatalogName key in the Linux and Mac OS X drivers.
www.simba.com 6
Updated the "Enable Transactions" configuration option
The "Enable Transactions" option is no longer available in the user interface of the
Windows driver. This option is now configured in the Windows Registry by adding the
"EnableTransactions=1" value to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Simba\Simba Salesforce ODBC Driver\Driver
For the Linux and Mac OS X drivers, this option must be configured in the
simba.salesforceodbc.ini file.
Updated key names for the "Proxy Username" and "Proxy Password" configuration options
The key for the "Proxy Username" option is now "ProxyUsername", and the key for the
"Proxy Password" option is now "ProxyPassword".
Resolved Issues
Parameters do not work properly when you run DML statements with filter passdown
Version 1.1.19
Implemented new "Enable Transactions" configuration option
You can now enable the driver to simulate transactions for applications that require
transaction support. To configure this option, use the "Enable Transactions" check box in
the Windows driver or the EnableTransactions key in the Linux and Mac OS X drivers.
Resolved Issues
Incorrect results returned if a query containing parameter filters is prepared once and executed
multiple times
www.simba.com 7
Version 1.1.18
Added the ability to execute INSERT, UPDATE, and DELETE statements
You can now modify data by executing INSERT, UPDATE, and DELETE statements through
the driver.
Improved performance when handling queries that contain an OR operator in a WHERE clause
The driver now provides better performance when handling queries that contain an OR
operator in a WHERE clause.
Improved performance when executing joins and subqueries
The driver now provides better performance when executing joins and subqueries. This
improvement is due to the driver fetching less data from Salesforce when executing joins
and subqueries.
Resolved Issues
Some stored procedures return empty result sets
This issue has been resolved. The issue occurred because tabular results were not being
handled correctly.
When connecting to Salesforce, the Login URL must be provided
This issue has been resolved. The new default behavior of the driver is to use
login.salesforce.com without prompting you to provide a URL. In the Windows version of
the driver, the Login URL field has been moved to the Advanced Options dialog box.
Version 1.1.17
User name and URL settings added to the DSN configuration dialog box
www.simba.com 8
In the DSN configuration dialog box, you can now set the user name and URL to use for
the connection.
Resolved Issues
Sample DSN that is installed with the driver uses an incorrect default URL
This issue has been resolved. The sample DSN now uses the correct URL.
When issuing queries that contain a cross-join between two tables, these tables are cross-joined
to an outer join of two other tables
Errors occur when using asynchronous ODBC functions in Qlikview
When using Qlikview with ODBC drivers, the program has problems with executing some
asynchronous ODBC functions. This issue has been resolved. As a workaround,
asynchronous support is now disabled when the driver is used in Qlikview.
Version 1.1.16
Resolved Issues
Maximum name lengths of catalogs, schemas, tables, columns, and procedures are not returned
correctly
Version 1.1.15
Support added for SOQL date literals
The SOQL parser now supports date literals, improving query handling.
www.simba.com 9
Version 1.1.14
Support added for Base64 data
The driver now supports Base64 data and exposes it as SQL_LONGVARBINARY. Issues
involving the column length for this data type have been resolved, and support for
iterative retrieval has been added.
Resolved Issues
Errors occur when using SOQL queries
A number of issues involving SOQL queries have been resolved, and the handling of SOQL
queries has been improved.
Version 1.1.13
Resolved Issues
In the Windows version of the driver, the connection dialog box does not return UID and PWD
correctly
Version 1.1.12
Resolved Issues
SQLProcedures cannot return both standard and custom Salesforce.com reports
This issue has been resolved. The driver can now return both types of reports at the same
time.
www.simba.com 10
Version 1.1.11
Resolved Issues
Driver terminates unexpectedly when the number of SOQL result items returned by Salesforce is
less than the number of columns in the ODBC result set
Result set columns sometimes returned in incorrect order
Result set columns may be returned in an order that is different from the order specified
in the select list of the SOQL query. This issue has been resolved, and the columns are now
returned in the expected order.
Version 1.1.10
Support added for Salesforce API version 30
The driver now supports Salesforce API version 30.
Improved handling of driver libraries
All the necessary third-party libraries are now statically linked to the Linux and Mac OS X
versions of the driver. You no longer need to specify the driver's lib directory in the
LD_LIBRARY_PATH environment variable (for Linux) or the DYLD_LIBRARY_PATH
environment variable (for Mac OS X).
Version 1.1.9
More information included in logging functionality
The logging functionality now logs the application that loaded the driver and the bitness
of the application.
www.simba.com 11
Resolved Issues
Driver terminates unexpectedly when handling multiple rows that are of varying size and contain
special characters
Driver terminates unexpectedly when retrieving certain reports
When the driver tries to retrieve a report and encounters a server error, an empty result set is
returned and no errors are reported
This issue has been resolved. The driver now displays an error message when it encounters
a server error.
Reports fail to execute
This issue has been resolved. The issue was caused by an invalid secure header flag in the
request issued to Salesforce; this flag has been removed.
Version 1.1.8
SanitizeCatalogName configuration option added
You can now use the SanitizeCatalogName option in a connection string to remove
invalid SQL-92 identifier characters from catalog names and replace spaces with
underscores.
Resolved Issues
Some relationship queries in SOQL cause trailing fields to return incorrect data
www.simba.com 12
Version 1.1.7
Resolved Issues
Some types of relationships in SOQL queries do not work as expected
When the query is parsed as SQL, datetime literals may fail when used in comparisons with
columns
Version 1.1.6
Support added for Mac OS X platform
You can now use the driver on Mac OS X machines.
Version 1.1.5
Support added for Salesforce API version 29
The driver now supports Salesforce API version 29.
Version 1.1.4
Resolved Issues
Reports do not display as expected when the UseAnalyticApi option is set to "1"
This issue has been resolved. The way that the driver retrieves lists of reports has been
changed to match the method recommended by Salesforce.
www.simba.com 13
Version 1.1.3
Improved performance for multi-table queries
The driver now uses gSoap connection pooling, which improves the performance of multi-
table queries.
Support added for Salesforce Analytics API
You can now use the Salesforce Analytics API for reports. Because some reports may not
be accessible through this API, you also have the option of reverting to the original driver
behavior and accessing reports through a URL instead.
Resolved Issues
Some queries return incorrect tables
A small memory leak occurs
Version 1.1.2
Support added for case-insensitive identifiers for SQL queries
You can now use case-insensitive column names and tables names in SQL queries.
Version 1.1.1
www.simba.com 14
Improved DSN configuration dialog box
The information and functionality provided in the DSN configuration dialog box have
been improved.
Version 1.1.0
Version 1.1.0 was the initial release of Simba Salesforce ODBC Driver with SQL Connector.
www.simba.com 15
Contact Us
If you have difficulty using the driver, please contact our Technical Support staff. We welcome
your questions, comments and feature requests.
Technical Support is available Monday to Friday from 8 a.m. to 6 p.m. Pacific Time.
Important: To help us assist you, prior to contacting Technical Support please prepare a detailed
summary of the client and server environment including operating system, product version, patch
level and configuration.
You can contact Technical Support via:

• E-mail: support@simba.com
• Web site: www.simba.com
• Telephone: (604) 633-0008 Extension 3
• Fax: (604) 633-0004
You can also follow us on Twitter @SimbaTech
www.simba.com 16

Release Notes Simba

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Release Notes Simba

Hochgeladen von

Copyright:

Verfügbare Formate

Release Notes

Simba Salesforce ODBC Driver with SQL Connector

This issue has been resolved.

Enhancements & New Features

Salesforce Professional Edition now supported

This issue has been resolved.

This issue has been resolved.

This issue has been resolved.

Enhancements & New Features

Salesforce API version 34 now supported

Aliases now supported

The driver now supports the use of aliases in SOQL queries.

Enhancements & New Features

Updated dialog box names in the Windows driver

Enhancements & New Features

Updated the default location of the simba.salesforceodbc.ini configuration file

By default, the simba.salesforceodbc.ini configuration file is now located in the lib

Updated driver configuration process

SIMBAINI environment variable renamed to SIMBASALESFORCEINI

Implemented configuration option for specifying a security token

Updated "Test" functionality in the Windows driver

Renamed "Strip catalog name" configuration option

Updated "Proxy Port" field

Updated handling of Sandbox URLs

Enhancements & New Features

Updated to Salesforce API version 32

The driver now uses Salesforce API version 32.

Support added for passing down aggregations

Updated handling of the Currency and Percent data types

Implemented configuration option for returning data as SQL_WVARCHAR instead of

Updated Logging Options dialog box

Salesforce user names consist of a user ID and a domain (for example,

Driver incorrectly reports the length of Address data as 0

Driver incorrectly reports keys as non-unique for SQLStatistics

Enhancements & New Features

Added logging for connection attributes

Description of "Strip Catalog Names" in the documentation is inaccurate

Enhancements & New Features

Implemented new "Strip Catalog Names" configuration option

Updated the "Enable Transactions" configuration option

HKEY_LOCAL_MACHINE\SOFTWARE\Simba\Simba Salesforce ODBC Driver\Driver

This issue has been resolved.

Enhancements & New Features

Implemented new "Enable Transactions" configuration option

This issue has been resolved.

Enhancements & New Features

Added the ability to execute INSERT, UPDATE, and DELETE statements

Improved performance when executing joins and subqueries

Some stored procedures return empty result sets

When connecting to Salesforce, the Login URL must be provided

Enhancements & New Features

This issue has been resolved.

Errors occur when using asynchronous ODBC functions in Qlikview

This issue has been resolved.

Enhancements & New Features

Support added for SOQL date literals

Enhancements & New Features

Support added for Base64 data

Errors occur when using SOQL queries

This issue has been resolved.

SQLProcedures cannot return both standard and custom Salesforce.com reports

This issue has been resolved.

Result set columns sometimes returned in incorrect order

Enhancements & New Features