The date and time of 1899/12/30 12:00:00 AM was not handled correctly as a fixed start of the axis range.

When a join with Salesforce tables was created using one of the tables twice, fields hidden in the first instance of the table were also hidden in the second table after creating an extract.

View filters disappeared after renaming a field in a database and replace references was performed.

When the Teradata driver was loading, a possible crash was experienced due to a race condition with the driver.

The create extract and preview join data window would sometimes be unresponsive with the 'loading' status when a spatial file was joined with a CSV file.

User calculations and parameters with fixed precision numbers would sometimes not return the correct results from the database.

Schema name list was not in order when connected to Amazon Redshift.

An LOD calculation that references another calculation containing a constant would sometimes have a different result after a data source was published.

In some cases, it was not possible to refresh subscription keys before the expiration date occurred.