--- title: "Release Note 2026-08" slug: "release-note-2026-08" description: "Discover the August 2026 release notes covering platform-wide enhancements, advanced database replication methods, expanded connector updates, and bug fixes." updated: 2026-09-15T20:34:04Z published: 2026-09-15T20:34:04Z canonical: "docs.dataddo.com/release-note-2026-08" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt > Use this file to discover all available pages before exploring further. # Release Note 2026-08 The August 2026 release extends a number of existing connectors with new datasets and fields. It also introduces a debug logging feature for easier troubleshooting, expands the Dataddo MCP Server, and adds three interface refinements and a broad batch of bug fixes. These updates reflect our continuous focus on improvements that make the platform a more stable and user-friendly experience. ## Connectors **New Connectors:** - Adobe Analytics - Gerimedica - Google Cloud Storage - Heuréka - Hotel Key **New Datasets, Attributes, and Metrics:** - **Amazon Ads/DSP**: Added a new report type. - **Exact Online**: Added a new **Bulk Accounts** dataset. - **Google Ads**: - Added a new `Asset group` report type, covering **Performance Max** asset groups. - Added the `all_conversions_from_location_asset_store_visits` metric to the **Store Visits** dataset. - **Google Display & Video 360**: Added a new **DV360 Reach/Frequency by Insertion Order** dataset, with a dynamic schema. - **Google My Business**: Added the `Services list` field to the **Locations** dataset. - **Gusto**: Added a new **Employee Work Addresses** dataset. - **Instagram Organic**: - Added the missing `media_url` field to the **Story Lifetime Insights**, **Carousel Post Lifetime Insights**, and **Post Lifetime Insights Image** datasets. - Added the missing `views` metric to the **Story Lifetime Insights** and **Post Lifetime Insights Image** datasets. - **JSON and JSON Universal**: Added the `dataddo_hash` metadata field. - **Microsoft Dynamics 365**: - Added `Potential Customer` and `Segment` fields to the **Accounts** dataset. - Added `Source Campaign`, `Last incoming email`, and `Last outgoing email` fields to the **Leads** dataset. - Added `Age`, `Deal Category`, `Est. close date`, `Stage Name`, `Silence`, `Est. Revenue`, `Est. Revenue (Base)`, `Partner`, `Status`, `Status Reason`, `Actual Close Date`, `Actual Revenue`, `Actual Revenue (Base)`, `Quote Sent On`, and `Source Campaign` fields to the **Opportunities** dataset. - Added `Owner` and `Created On` fields, available on both the **Accounts** and **Opportunities** datasets. - Added `Country` and `Action Date` fields to the **Accounts** dataset. - Added a `Source Capture` field, available on both the **Accounts** and **Leads** datasets. - **Pinterest Organic**: - Added a new **Top Pins Analytics** dataset. - Added a new **Daily Follower Snapshot** dataset, with support for `Use Extraction Timestamp`. - **Shiftbase**: Added a new **Plus & Min Daily** dataset. - **Unbounce**: The **Leads** dataset now unwinds the `emails` array field into individual rows. **Connector Updates:** - **Google Ads**: Upgraded the API from the sunsetted `v21` version. - **Gusto**: Migrated all datasets to a more stable API version. - **HubSpot** (destination): Added support for writing to the **Companies** CRM object, alongside the existing **Contacts** and **Deals** objects. - **LinkedIn Organic**: The `page_followers_count` dataset now supports extracting data for multiple company pages under one authorization, instead of just one. - **TikTok Ads**: The **Insights / Reporting API** source now supports an `ad_status=STATUS_ALL` option ("Include deleted ads"), so deleted or paused ads can be included in extraction. ## New Features ### Debug Logs A new **show debug logs** feature lets you view a full list of API calls and extraction details behind a source, right from the Dataddo UI. It currently covers extraction requests, with database operations (e.g. SQL queries) planned next. It's a quick way to see exactly what happened during a run without waiting on support. ## Platform Updates ### Expanded MCP Server Tooling Additional tooling is being added to the Dataddo MCP Server beyond catalog search and documentation retrieval, such as data discovery, pipeline maintenance, and pipeline debugging. This allows us to extend support for AI coding assistants such as Claude Code. See the [MCP Server documentation](https://docs.dataddo.com/docs/dataddo-mcp-server) for more information. ### New Column Data Types Four new column data types are now available — `timestamp_tz`, `timestamp_ms`, `datetime_ms`, and `decimal`. This means timezone-aware timestamps, millisecond-precision times, and exact decimal values can now be represented natively in your schema, instead of being approximated or reformatted after extraction. ### ZIP File Support File type connectors now accept `ZIP` archives directly as a supported format. This means compressed exports can be loaded straight into a flow, without an extra step to unpack them first. ## UX/UI Enhancements ### Folder Picker Improved the folder and file pickers used across SFTP, S3, SharePoint, and other connectors. There is now a visible pointer on selectable items, and unselectable files are greyed out. ![Improved file path picker in file type connectors.](https://cdn.document360.io/084ed225-3f99-4644-a2da-39ca0cd5ef45/Images/Documentation/Improved%20file%20picker.png) ### Member ID Visibility The **Team Members** section can now show each member's member ID, useful for headless or API setups without needing database access. Click on **Customize columns** and toggle the ID. ![Enable the ID column to display team members IDs.](https://cdn.document360.io/084ed225-3f99-4644-a2da-39ca0cd5ef45/Images/Documentation/Visible%20team%20members%20ID.png) ## Bug Fixes ### Connector Fixes **AWS S3**: - Fixed destination creation not surfacing validation errors (e.g. invalid credentials) in the UI, letting users believe the destination was configured correctly when it wasn't. **Azure SQL**: - Fixed flows failing with an Avro decoder error (`invalid block`). **Bitly**: - Fixed the connector never succeeding on its first extraction run, failing with missing `long_url` and `title` columns. Both were populated via `sharedValues`, which weren't included in the initial run's output rows. **Criteo**: - Fixed the **Statistics Report** dataset returning 0 rows when the date range exceeded 30 days. This was caused by an outdated API version with a low time-range limit. The connector's Criteo API version was upgraded and the limit increased. **Facebook Organic**: - Fixed the **Posts Lifetime Insights by Post** dataset failing with a `500 Internal Server Error` when some of the authorized pages lacked the required permissions. Extraction now tolerates individual page failures instead of failing outright. **Facebook Page Insights**: - Fixed the `page_follows` metric's value appearing in the `post_video_views_60s_excludes_shorter` column instead of its own. **Google Analytics 4**: - Fixed cloned sources sometimes pulling data from the wrong account. This was caused by the system sending both `propertyId` and `propertyIds`, creating a race condition with a backward-compatibility path on the backend. - Fixed selected property names not displaying in the source description, showing `PROPERTY=All properties and sub-properties` instead regardless of what was actually selected. **Gusto**: - Fixed the **Payroll Employee Taxes** and **Employee Benefits** datasets failing to extract data because the default date range isn't accepted by the Gusto API. **HubSpot**: - Fixed the **Email Statistics** and **Email Statistics – Campaign Aggregations** datasets failing with a `400 Bad Request`, caused by the connector requesting an invalid CRM object type from HubSpot's API. - Fixed HubSpot destination writes failing with a generic `context canceled` error instead of surfacing HubSpot's actual validation error (e.g., duplicate values in a field configured as unique). **Instagram Business**: - Fixed source creation/preview failing with a `406 Not Acceptable` error caused by unresolved date-range placeholders in the underlying insights request. **Instagram Organic**: - Fixed the **Media Insights – Reels** dataset failing to extract immediately after source creation. The dataset's default request policy now tolerates partial failures. **JSON Connector**: - Fixed the JSON Universal source form's main tabs not displaying correctly on load. - Fixed the JSON Universal filter tool breaking after clicking into the raw response, requiring the browser field to be reselected before filtering worked again. - Fixed a JSON source's inferred field data type changing between runs (e.g. `NUMERIC` to `FLOAT`), causing writes to Google BigQuery to fail with a schema-mismatch error. **Leadfeeder**: - Fixed historical backfills larger than 10,000 records failing with a `403 Forbidden` error, by loading data in smaller, 1-day intervals instead of Leadfeeder's default 30-day window. The underlying rate limit is enforced by Leadfeeder's own API. **LinkedIn Ads**: - Fixed sources pulling data for all ad accounts instead of only the one selected. **Microsoft Ads**: - Fixed source creation failing with `API_INTERNAL_SERVER_ERROR` when the `accountIds` field was sent as a string instead of an array. - Fixed sources extracting data for all advertiser accounts instead of only the selected `Advertiser ID`, caused by the selected ID not being saved to source metadata. **OneDrive**: - Fixed flows writing to OneDrive failing with a `REQUEST_VALIDATION_ERROR` on the date-time format field, caused by a mismatch between the date-format value sent by the writer configuration and what the underlying writer code expected. **QuickBooks**: - Fixed the authorizer unnecessarily requesting the `com.intuit.quickbooks.payment` OAuth scope, which blocked users without **Payments** configured from authorizing. **Salesforce Pardot**: - Fixed the issue with a Salesforce Pardot authorizer renaming. ### General Fixes **Abort processing errors**: - Fixed API errors not being shown to the user when aborting a running flow/source. **Data preview timeout**: - Fixed data preview showing a generic error dialog after 30 seconds even though the request was still completing on the backend. **DPE token exchange**: - Fixed the DPE token exchange endpoint returning an empty `customerID`, causing `invalid token: empty customerID in exchanged token` errors for customers using the DPE API directly. This was caused by the endpoint returning the wrong response type (missing `customer_id`), which didn't match what DPE's client expected. **Dynamic date range for future dates**: - Fixed the `{{dateRange}}` template placeholder returning incorrect data for future date ranges; it previously only worked when the date range was hardcoded directly into the request body. **Filters**: - Fixed reloading the page after unchecking a filter value (without deleting the filter itself) causing a `This value should not be blank` validation error, because the empty filter was still being sent in the request. **Invite permissions**: - Fixed non-owner account roles being able to invite new team members with any role. Only the owners or admins can now invite with full role options. Authorizer-role users retain a restricted invite option limited to the authorizer role. **Manual Data Load warning**: - Fixed a `don't load data will restart your source"` warning being shown on sources that don't have a configurable date range, where it doesn't apply. **Multi-Account Extraction**: - Fixed cloning a source with [Multi-Account Extraction](https://docs.dataddo.com/docs/multi-account-extraction) enabled resulting in an empty account list on the clone. **Source cloning**: - Fixed cloned sources saving both snake_case and camelCase versions of hash-column metadata (e.g. `hashColumns` and `hash_columns`), which caused hash columns to become mismatched after cloning. **Source creation buttons**: - Fixed buttons being stuck disabled when creating a source. **Source/flow picker in ticket creation**: - Fixed the source/flow picker in ticket creation only showing the ~20 most recently used items instead of the full, searchable list.