Changelog 06/22/2021 - 07/05/2021

_changelog-files/2021/2021-06-25-toggl-v1-update-base-urls.md

@@ -0,0 +1,13 @@
+---
+title: "Toggl (v1) update: Updated base API URLs"
+content-type: "changelog-entry"
+date: 2021-06-25
+entry-type: updated-feature
+entry-category: "integration"
+connection-id: toggl
+connection-version: 1
+pull-request: "https://github.com/singer-io/tap-toggl/pull/9"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+{{ this-connection.display_name }} has updated their API information. We've updated the base of the API URLs we use to extract data from to ensure we are pulling information from the correct enpoints. 

_changelog-files/2021/2021-06-28-facebook-ads-v1-update-country-primary-key.md

@@ -0,0 +1,27 @@
+---
+title: "Facebook Ads (v1) update: Fixed composite primary key for the `ads_insights_country` table"
+content-type: "changelog-entry"
+date: 2021-06-28
+entry-type: bug-fix
+entry-category: "integration"
+connection-id: "facebook-ads"
+connection-version: "1"
+pull-request: "https://github.com/singer-io/tap-facebook/pull/154"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+We've fixed the `ads_insights_country` composite primary key. The `country` field had previously been erroneously excluded.
+
+The composite primary key is now: `campaign_id : adset_id : ad_id : date_start : country`
+
+This is a breaking change and communiation from Stitch support has been emailed to affected users.
+
+If you are not already including the `country` field in downstream processes that identify uniqueness of records in the files loaded to S3 for this table, this field will need to be added into those processes.
+
+You may also wish to reset this table to have historical data re-replicated and more accurately portrayed in S3, in which case you should:
+
+  1. Contact our support team to implement a courtesy row-usage exemption for your Facebook Ads integration.
+  2. Within Stitch, navigate to the ads_insights_country table's Table Settings page.
+  3. Use the Reset Table button to queue this table's reset.
+
+If you have any questions about the change or this process, please reach out to Stitch support via in-app chat.

_changelog-files/2021/2021-06-28-github-v1-add-error-exception.md

@@ -0,0 +1,19 @@
+---
+title: "GitHub (v1) update: New empty response error exception"
+content-type: "changelog-entry"
+date: 2021-06-28
+entry-type: updated-feature
+entry-category: "integration"
+connection-id: "github"
+connection-version: 1
+pull-request: "https://github.com/singer-io/tap-github/pull/126"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+To improve the experience of our {{ this-connection.display_name }} integration, we've changed how we handle empty response errors.
+
+Instead of bypassing the error without an explanation, the integration will now raise an error and display it in the Extraction Logs:
+
+```shell
+HTTP-error-code: 400, Error: The request is missing or has a bad parameter.
+```

_changelog-files/2021/2021-06-28-outreach-v1-new-name-field.md

@@ -0,0 +1,15 @@
+---
+title: "Outreach (v1) update: New field!"
+content-type: "changelog-entry"
+date: 2021-06-28
+entry-type: updated-feature
+entry-category: "integration"
+connection-id: "outreach"
+connection-version: "1"
+pull-request: "https://github.com/singer-io/tap-outreach/pull/13"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+A new field has been added to our {{ this-connection.display_name }} (v{{ this-connection.this-version }}) integration!
+
+The `name` field is now available for replication in the `events` table.

_changelog-files/2021/2021-06-29-google-search-console-v1-empty-response-error-message.md

@@ -0,0 +1,19 @@
+---
+title: "Google Search Console (v1) update: New empty response error exception"
+content-type: "changelog-entry"
+date: 2021-06-29
+entry-type: updated-feature
+entry-category: "integration"
+connection-id: "google-search-console"
+connection-version: 1
+pull-request: "https://github.com/singer-io/tap-google-search-console/pull/21"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+To improve the experience of our {{ this-connection.display_name }} integration, we've changed how we handle empty response errors.
+
+Instead of bypassing the error without an explanation, the integration will now raise an error and display it in the Extraction Logs:
+
+```shell
+HTTP-error-code: 400, Error: The request is missing or has a bad parameter.
+```

_changelog-files/2021/2021-06-30-chargebee-v1-new-jsondecode-error-handling.md

@@ -0,0 +1,16 @@
+---
+title: "Chargebee (v1) improvement: New handling for JSONDecode errors"
+content-type: "changelog-entry"
+date: 2021-06-30
+entry-type: improvement
+entry-category: "integration"
+connection-id: "chargebee"
+connection-version: "1"
+pull-request: "https://github.com/singer-io/tap-chargebee/pull/51/"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+We've added new helpful error messages for the `invoices` and `transactions` streams when JSONDecode errors are encountered:
+
+- `Sorry, authentication failed. Invalid api key`
+- `Did not get response from the server due to an unknown error`

_changelog-files/2021/2021-06-30-chargebee-v1-new-price-tiers-attributes.md

@@ -0,0 +1,24 @@
+---
+title: "Chargebee (v1) update: New fields!"
+content-type: "changelog-entry"
+date: 2021-06-30
+entry-type: updated-feature
+entry-category: "integration"
+connection-id: "chargebee"
+connection-version: "1"
+pull-request: "https://github.com/singer-io/tap-chargebee/pull/53"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+We've added new fields to the `events` and `addons` tables.
+
+New to the `events` table:
+- `show_descriptions_in_invoices`
+- `show_description_in_quotes`
+- `object` subattribute within the `tiers` attribute
+
+New to the `addons` table:
+- `show_descriptions_in_invoices`
+- `show_description_in_quotes`
+- `object` subattribute within the `price_in_decimal` attribute
+

_changelog-files/2021/2021-06-30-chargebee-v1-remove-min-max-properties.md

@@ -0,0 +1,13 @@
+---
+title: "Chargebee (v1) update: restrictive properties removed"
+content-type: "changelog-entry"
+date: 2021-06-30
+entry-type: updated-feature
+entry-category: "integration"
+connection-id: "chargebee"
+connection-version: "1"
+pull-request: "https://github.com/singer-io/tap-chargebee/pull/45"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+We've removed all `minimum/maximum` and `minLength/maxLength` restrictive properties from all {{ this-connection.display_name }} tables so that the integration can continue to sync with the evolving {{ this-connection.display_name }} API.

_changelog-files/2021/2021-07-01-amazon-s3-csv-fix-empty-file-error.md

@@ -0,0 +1,15 @@
+---
+title: "Amazon S3 CSV (v1) bug fix: Empty file error handling"
+content-type: "changelog-entry"
+date: 2021-07-01
+entry-type: bug-fix
+entry-category: "integration"
+connection-id: "amazon-s3-csv"
+connection-version: 1
+pull-request: "https://github.com/singer-io/tap-s3-csv/pull/38"
+---
+{{ site.data.changelog.metadata.single-integration | flatify }}
+
+Previously, the {{ this-connection.display_name }} integration would not complete a replication job when multiple CSV files in an S3 bucket had empty records - even if there were some files that did have records.
+
+This has been corrected. The integration will now complete replication jobs by ignoring the files without records.