Salesforce Pardot Release Notes

Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.

See TIBCO Scribe® Online Connector For Salesforce Pardot for more information.

Note: To access any changes to metadata support, such as new operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata.

 

Version 1.6.0

Released April 5, 2022.

New And Noteworthy

Changes In Functionality

Closed Issues

SCPARD-263

The Salesforce Pardot connector does not support Create/Update Lists. They are now supported using the HTTP Request to the REST API.

SCPARD-267

When updating a Prospect with a score greater than 200, an object reference error similar to the following is generated:

Error description: Operation failed. Label: Update Prospect, Name: ProspectUpdate
Message : Object reference not set to an instance of an object.

SCPARD-269

Users cannot select a production URL and authenticate using a sandbox URL, which is required in some cases.

SCPARD-426

Improved concurrency error detection when concurrent requests to the Salesforce Pardot API have been exceeded during a Query or Query Preview. (Case # 02054854)

Known Issues

SCPARD-163

Summary: If the access token for the connection expires and cannot be refreshed, for example if there is a network outage, the connection does not recover and an error similar to the following is generated: Failed to Re-authenticate

Workaround: Open the Connection dialog, select Authenticate, go through the authentication process, and save the Connection.

60244

Summary: Errors generated when the Salesforce Pardot daily API limit is reached do not clearly indicate the cause of the error. For example, you might see Operation returned no results or Operation failed errors.

Workaround: Check your Salesforce Pardot account to see if you have reached your API limit when troubleshooting errors. If the limit has been exceeded, run the app at a later date.

Version 1.5.0

Released March 15, 2021.

New And Noteworthy

Changes In Functionality

SCPARD-188 / SCPAR-189

If you modify an existing Salesforce Pardot Connection, you must select Authenticate on the Connection dialog and go through the authentication process. If you save the changes to the Connection without authenticating, when your Maps run, exception errors are generated. After this initial re-authentication, any time you make changes to the Connection and try to save the Connection without authenticating, you are prompted to re-authenticate.

Closed Issues

SCPARD-190

When the Prospect entity has a large amount of history, an initial query of the Prospect entity timed out or indicated that the Prospect was not found. (Case # 01926474)

Version 1.4.1

Released February 9, 2021.

New And Noteworthy

There are no new features in this release.

Changes In Functionality

Authentication

On February 15, 2021, as part of the Salesforce Spring ‘21 release, the current Pardot user authentication system will be deprecated. All users will be required to use Salesforce single sign-on (SSO). Users who have not enabled Salesforce SSO will not be able to log into Pardot as of February 15, 2021.

Warning: Once Pardot users have been converted to Salesforce SSO their Pardot user credentials are no longer valid and the Connector for Salesforce Pardot will not be able to connect using Pardot authentication. You must update your existing Salesforce Pardot Connections or create new ones to use the new authentication method.

Existing Salesforce Pardot Connections will continue to work until the Pardot user authentication system is deprecated or you update your authentication method to Salesforce SSO.

When you update your authentication method to Salesforce SSO, there are two additional requirements to connect to Salesforce Pardot.

Salesforce has provided some information about this transition with guidance on updating your Pardot users.

Pardot User Migration Overview

Pardot User Migration Guide

Business Unit ID

The Pardot API will require a Business Unit ID to access your Pardot data. This field has been added to the Salesforce Pardot Connection dialog. You must update your existing Salesforce Pardot Connections or create new ones to include the Business Unit ID.

To find your Pardot Business Unit ID, go to your Salesforce Setup and search for "Pardot Account Setup". Your Pardot Business Unit ID begins with "0Uv" and is 18 characters long.

If you do not have a Business Unit ID, contact your Salesforce Administrator for help. See the following Salesforce Pardot article for additional information: Pardot Authentication

Closed Issues

SCPARD-22

Using a Lookup Block to query Prospect by email generates errors similar to the following: (Case # 01873961)

ERROR: Exception Type : OverflowException
Message : Value was either too large or too small for an Int32.

SCPARD-12

Writing to multi-select picklists is not supported. (Case # 01825445)

SCPARD-5

Fetch Blocks that filter data by Prospect email only return a single record instead of all matching records. (Case # 01747637)

 

Version 1.3.1

Released March 25, 2019.

New And Noteworthy

Closed Issues

68067 / 66474 / 66376

Changed the data type to nullable long for the Visitor entity screen height and screen width fields. These fields were set as nullable int data type, causing errors similar to the following: (Case # 65776)

Value was either too large or too small for an Int32
Note: For this change to take effect you need to reset metadata for your Salesforce Pardot Connection.

66183 /65670 / 65157

Added retry logic and error handling to handle Operation Timeout and Connection Closed errors when Querying. (Case # 65357)

63518 / 63316 / 63317

Query results for Prospect Custom fields were limited to 200 fields, therefore Querying Prospects sometimes did not provide the Custom fields required for a specific integration. (Case # 64505, 69597, 69556)

Note: For this change to take effect you need to reset metadata for your Salesforce Pardot Connection.

63424 / 63423 / 62533

When retrieving large datasets that exceeded the allotted amount of time for the Connection to be open, the Connection was automatically closed before the app finished executing causing Object Reference errors. (Case # 64373)

 

Version 1.2.1

Released February 21, 2018.

New And Noteworthy

There are no new features in this release.

Closed Issues

56591, 57996

Enhanced methods used to query entities to handle returning large sets of data and prevent ambiguous errors, such as: Object reference not set to an instance of an object. (Case # 62264, 63106)

 

Version 1.1.0

Released May 2, 2017.

New And Noteworthy

Added support for the following:

Closed Issues

10528

Improved performance of the Remove operation for Listmembership. (Case # 76798)

39221

In some cases, users were unable to modify their password in the TIBCO Cloud™ Integration - Connect Connection dialog for Salesforce Pardot. (Case # 56839)

 

September 19, 2014 Release

New And Noteworthy

The Connector for Salesforce Pardot supports the following:

Closed Issues

There are no Closed Issues in this release.

Related Topics

Release Notes And Known Issues