The highly skilled product team at DataBlend releases new connectors and updates monthly. It's our way of keeping the product fresh and up-to-date with the latest connectors and improvements. Below is a brief outline of the newest release. See our release notes: https://lp.datablend.com/knowledge/release-notes-1
Existing Connector Updates
There is a reason why DataBlend is trusted by the top finance and accounting departments at over 1200 companies. Our impressive product team is committed to updating and improving our growing number of connectors, enabling users to have fast, reliable, and secure integrations between their everyday applications in the Office of Finance.
With this brand-new DataBlend release, we've updated the following connectors:
ADP WFN Classic
- Collector: Fixed an issue where the GL Document Collector's "Parse as CSV" toggle remained active even when hidden, causing non-CSV documents to be incorrectly parsed as CSV
- Collector: Updated the Onboarding Collector to support multiple comma-separated Context Expression IDs, allowing collection across multiple onboarding contexts in a single run
- Collector: Fixed an issue where running the Time Collector with no date filter returned fewer rows than when an end date filter was applied; the filterless query now correctly returns all available records
Concur
- Data Target: Fixed an issue where the Attendee Data Target Upsert mode failed to detect records that needed to be created, only updating existing records
- Data Target: Added API version selection to the Attendee Data Target, allowing users to choose between the existing V3 and the new V4 endpoint
- Data Target: Fixed an issue where the Bulk User Data Target Update mode failed with "Missing 'Operations' in the patch body"; corrected the PATCH request body format to match the Concur SCIM API requirement
- Connector: Fixed an issue where 403 Forbidden responses from Concur dropped the API's error message from the job log, making it difficult to diagnose permission-related failures
D365: Business Central
- Connector: Hardened collectors and data targets against degenerate inputs (null or malformed field values) that previously caused unhandled exceptions during collection or data target execution
Dynamics 365 CRM
- Collector: Fixed an issue where the collector editor allowed
$expand configurations that could never successfully run, and showed a blank Type for collectors created via the API; invalid configurations are now prevented at save time and the Type field is correctly populated
- Collector: Added support for using D365 Views (both system and personal saved views) as a collection source, allowing users to collect records pre-filtered by an existing CRM view
- Connector: Fixed an issue where Dataverse throttling responses (429 / 503) caused collectors and data targets to fail immediately instead of retrying; added Polly-based retry-with-backoff on throttle responses
Procore
- Collector: Added
origin_code field to the Contract Payment Collector schema
- Collector: Fixed an issue where the Company Vendors (Show) Collector in all-vendors mode no longer returned show-only fields such as
invoice_contacts following a prior fix; these fields are now correctly included again
- Connector: Fixed an issue where the Procore ClientController bypassed the standard API controller pipeline, skipping auth policy enforcement, centralized error handling, and request validation; all Procore API calls now flow through the standard pipeline
- Connector: Hardened collectors and data targets against degenerate inputs that previously caused unhandled exceptions
QuickBooks Online
- Connector: Updated the QuickBooks Online plugin off the legacy SDK to support the new GraphQL-based Intuit API, ahead of the SDK deprecation
- Collector: Added a Projects Collector using the QuickBooks Online Projects endpoint
- Data Target: Fixed an issue where multi-record Data Target files were merging, duplicating, or dropping records; journal entry lines were being posted twice due to incorrect record grouping in the file processor
- Connector: Hardened collectors and data targets against degenerate inputs that previously caused unhandled exceptions
- Credential: Fixed an issue where the OAuth connection failed with "credentialId is required" when Intuit rejected the project-management scope during authorization; the scope request is now handled gracefully when not supported by the connected company
Rillet
- Connector: Hardened collectors and data targets against degenerate inputs that previously caused unhandled exceptions
- Collector: Added Multi-Book support, including a new List Books Collector and a
book_id parameter on report and journal entry Collectors, allowing data to be collected from specific accounting books
- Collector: Added an Executive P&L Collector; added status and currency filter options to the Products Collector
- Connector: Addressed remaining Rillet V4 API gaps, including missing endpoints, additional filter options, and missing contract and customer write fields on Data Targets
Sage Intacct
- Collector: Added automatic batching of comma-separated parameter values to 1,000 items per API call, preventing errors when parameter lists exceed the Intacct API's per-request limit
- Collector: Fixed an issue where the Account Balances, Account Balances By Dimensions, and AR Aging Collector editors wrote parameter paths without the required
/configuration prefix, causing parameters to not be applied correctly at runtime
- Collector: Fixed an issue where the List Account Balances by Dimensions Collector errored when parameters were supplied; corrected the parameter path handling to match the expected API format
- Data Target: Fixed an issue where the AR Invoice Data Target errored when sending custom exchange rates; corrected the XML element structure for the custom rate fields
Sage Intacct REST
- Collector: Fixed an issue where the Query Collector offered fields that the Intacct REST query service cannot query, causing collection errors when those fields were selected; non-queryable fields are now excluded from the field picker
- Data Target: Fixed an issue where the Journal Entry Data Target Update mode had no line key column available, making it impossible to target an existing journal entry line for update; added the required line key column to the Update mapping
- Data Target: Fixed an issue where line-level custom fields on the Journal Entry and Order Entry Data Targets were sourced from the first grouped row rather than each individual line's row, causing incorrect custom field values to be written for all lines after the first
Salesforce REST & SOAP
- Credential: Updated the Salesforce SOAP credential to use OAuth-based authentication ahead of Salesforce's deprecation of the legacy username/password SOAP login flow
- Connector: Hardened collectors and data targets against degenerate inputs that previously caused unhandled exceptions
SharePoint
- Collector: Cleaned up the Schema Name options in the Download Files Collector to remove stale or duplicate entries and improve clarity when selecting a destination schema
- Data Target: Added the ability to manually enter a Drive ID and Site ID on the Upload Files Data Target, supporting configurations where the dropdown cannot enumerate the target site or drive
- Data Target: Added an option to automatically create destination folders on the Upload Data Target when the specified folder path does not already exist
- Connector: Hardened collectors and data targets against degenerate inputs that previously caused unhandled exceptions
Stripe
- Data Target: Added Subscriptions and Subscription Items Data Targets supporting Create and Update operations
- Data Target: Fixed an issue where the Payment Intent Data Target rejected JSON-array cell values (e.g.,
payment_method_types) when dot-notation columns were also present in the query; array-valued cells are now correctly serialized alongside nested object fields
- Connector: Hardened collectors and data targets against degenerate inputs (null, empty, or malformed field values) that previously caused unhandled exceptions
WooCommerce
- Connector: Added WooCommerce Data Target field metadata to the Data Target Metadata API, enabling query result validation and field suggestions in the UI for WooCommerce Data Targets
UI Updates
- Added a record count column to the Collector Jobs history list, showing how many records were collected in each run without needing to open the job detail
- Fixed an issue in the Query Builder where a WITH query's Aliased Relation was incorrectly replaced by a "Reference" Table when reopening the query, causing the query to fail validation or produce incorrect SQL
- Added a "Data Target Fields" drawer to the Query editor, allowing users to view the expected fields and types for a linked Data Target directly alongside the query they are building
- Added Procore Data Target field metadata to the Data Target Metadata API, enabling query result validation and field suggestions in the UI for Procore Data Targets