# Version 4.6 Now Available!
# Enhancements
# TM1Connect Server Enhancements
- Ability to connect to a Planning Analytics cloud instance
Users can now point TM1Connect to a Planning Analytics instance hosted in IBM cloud and use their IBM credentials to authenticate.
- Overall performance improvement
TM1Connect now uses data compression when communicating to the specified Planning Analytics instance via OData API. This provides substantial overall performance improvement and better user experience.
- Major performance improvement in the TM1Connect Manager
Performance improvement during the initial load of objects after initially logging into the TM1Connect Manager. This has been achieved by applying performance optimizations and reducing the number of requests issued when loading the objects.
- Ability to specify SSL/TLS configuration values
When TM1Connect is configured to use SSL/TLS when communicating with TM1 view OData API, users can now supply the following custom values to use for the secure communication: a list of SSL/TLS ciphers and the SSL/TLS version to use.
- Publishing private views
Users are now able to publish private views in the TM1Connect Manager.
# ODBC Driver Enhancements
- Microsoft SQL Management Studio support
Added support to use TM1Connect ODBC driver within Microsoft SQL Management Studio to pull TM1 data.
# Bug Fixes
- Export start date/time disappears
Specified value for the starting date/time of a view export no longer disappears after triggering an export by clicking the "Save and Run Now" button.
- Selected export days not being saved in the scheduler.
When selecting specific days for a view export under "Scheduler" section in the TM1Connect Manager, specified values are properly saved and used when exporting view data.
- When specifying a username prefixed with a domain, application fails to launch
Users can now specify a TM1 username in the following format when configuring a TM1Connect instance using the configuration utility: domain\username.
- Specifying a hierarchy root member does not work when including hierarchy
When including hierarchy for a view dimension in the TM1Connect Manager and specifying a custom hierarchy root member, correct hierarchy is displayed, which starts from the specified parent.
# Known Issues
None
# Version 4.4
# Enhancements
# TM1Connect Server Enhancements
- Added request caching
Any requests for data from TM1 which are similar to a previously requested query are resolved from a temporary cache rather than performing a subsequent request. For example, if two views use the same dimension and attributes, TM1Connect will only perform the dimension request once, even though the views are queried separately.
- Added request caching
Any requests for data from TM1 which are similar to a previously requested query are resolved from a temporary cache rather than performing a subsequent request. For example, if two views use the same dimension and attributes, TM1Connect will only perform the dimension request once, even though the views are queried separately.
- Log settings accessible from TM1Connect Manager
Enabling and disabling logging and tracing can now be done by the Manager rather than manually editing the configuration file. Also, any changes made in the Manager settings will become effective immediately and will not require restarting of the server.
- Improve SQL Syntax Support
Added support for multiple conditions in SQL queries containing IN and NOT in clauses. Multiple WHEN statements are now allowed within a CASE statement. Boolean data type are supported in SQL Queries.
- Added Version Update Check
TM1Connect will now check for updates periodically in the TM1Connect Manager UI and will notify administrators when a new version can be downloaded and installed.
# ODBC Driver Enhancements
- Added Kerberos integrated authentication
ODBC driver now supports integrated authentication using Kerberos. Any client applications connecting to TM1Connect using the driver will not need to supply a username or password to access TM1 data.
# TM1Connect Configuration Enhancements
- Improved error reporting
When an error occurs while using the TM1 REST API, error messages now show the underlying error generated by TM1.
# Data Agent Enhancements
- Output to subdirectories
Ability to specify sub-directories for output file destination
# Bug Fixes
- Fixed SQL Issues
DateTime data types working properly when client is in a different time zone from server.
- Integrated Authentication
User name is no longer required to be specified in the configuration in order for the integrated authentication to work.
- TM1 Rest API using SSL
In the TM1Connect configuration utility, users can now test the TM1 Rest API URLs that are using HTTPS protocol without a timeout occurring.
# Known Issues
None