Contact Free trial Login

Salesforce Marketing Cloud Connector Release Notes - Mule 4

Support Category: Select

The Salesforce Marketing Cloud connector lets you connect to the Salesforce Marketing Cloud web services using the Salesforce Exact Target API. This connector exposes convenient methods for managing objects and calling services provided by the Salesforce Exact Target API, also known as Salesforce Marketing Cloud.

2.2.0

October 1, 2019

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7 and later

Fuel SDK

v1.2.2

Fixed Issues

  • Fixed a bug where sensitive information was displayed in logs by making logging optional. You can enable logging by using the new Enable Soap Logging parameter in the connector configuration. (SE-13059)

2.1.5

August 8, 2019

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7 and later

Fuel SDK

v1.2.2

Features

  • Upgraded the File Connector dependency to version 1.3.0. (CONN-2523)

Fixed Issues

  • The Salesforce Marketing Cloud Connector was throwing the UNKNOWN error on an invalid query. The error handling has been improved and now, when a query is invalid, the correct exception is thrown. (SE-12523)

2.1.4

May 29, 2019

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7 and later

Fuel SDK

v1.2.2

Fixed Issues

  • Salesforce Marketing Cloud Connector did not parse queries correctly. The connector now translates an SOQL query correctly when including a clause in parentheses. (SE-11721)

2.1.3

May 6, 2019

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7 and later

Fuel SDK

v1.2.2

Fixed Issues

  • SFMC (Salesforce Marketing Connector) no longer erroneously appends a timestamp to the value in a SQL statement(SE-11603).

  • Now works with Mule 4.2.0 and Java 11. Added the following missing dependencies: com.sun.xml.messaging.saaj:saaj-impl:1.5.1, javax.ws.rs:javax.ws.rs-api:2.1.1 and javax.xml.ws:jaxws-api:2.3.1

2.1.2

March 11, 2019

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7 and later

Fuel SDK

v1.2.2

Fixed Issues

  • Cannot connect to Salesforce Marketing: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog. This issue was fixed by wrapping the thrown exception with a more readable one, SFDC-MARKETING-CLOUD:UNKNOWN.

2.1.1

February 7, 2019

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7 and later

Fuel SDK

1.2.2

Fixed Issues

  • Fixed error in parser date.

2.1.0

November 20, 2018

The Salesforce Marketing Cloud connector is compatible with:

Compatibility

Application/Service Version

Mule

4.1 and later

Anypoint Studio

7 and later

Fuel SDK

1.2.2

Features

  • Support for Salesforce Marketing Cloud API v43 based on Fuel SDK v1.2.2.

2.0.0

January 19, 2018

Release notes for the Salesforce Marketing Cloud connector.

Compatibility

The Salesforce Marketing Cloud connector is compatible with:

Application/Service Version

Mule

4.0 and later

Anypoint Studio

7 and later

Exact Target API

v145.3

Features

  • Configure Create - Calls the "Configure" command with "Create" as the action attribute when connected to the Marketing Cloud SOAP web service.

  • Configure Delete - Calls the "Configure" command with "Delete" as the action attribute when connected to the Marketing Cloud API SOAP web service.

  • Configure Update - Calls the "Configure" command with "Update" as the action attribute when connected to the Marketing Cloud API SOAP web service.

  • Create - Creates a new object on the Marketing Cloud API web server.

  • Delete - Deletes an existing object on the Marketing Cloud API web server.

  • Perform get max count - Calls the "Perform" command with "GetMaxCount" as the action attribute when connected to the Marketing Cloud API SOAP web service.

  • Perform start - Sends a "Perform" command having "Start" as an action attribute when connected to the Marketing Cloud API SOAP web service.

  • Perform stop - Sends a "Perform" command having "Stop" as an action attribute when connected to the Marketing Cloud API SOAP Web service.

  • Retrieve - Retrieves objects from the Marketing Cloud API web server in a SQL query-like fashion.

  • Schedule start - Calls the "Schedule" command with "Start" as the action attribute when connected to the Marketing Cloud API SOAP web service.

  • Update - Updates an existing object on the Marketing Cloud API web server.

  • Upsert - Creates an object if the object does not already exist, or delete an existing object on the Marketing Cloud API web server. This operation is achieved by using "Create" method of the Marketing Cloud API SOAP API.

Fixed Issues

This is the first version of the connector, thus no fixes were required; there are only new features.

Known Issues

Providing a Subclass as Type To a Complex Field

Some objects have complex fields that represent a base class from Salesforce Marketing. So, if instead of the base class, you want to pass a subclass of it as value to that field, that is not possible because the connector is not recognize the fields that do not belong to the base class. You must manually map those fields in Transform Message and add a field named "concreteClassType" with the name of the subclass as value. For more information and an example, read the connector guide.

Retrieving Fields From a Hierarchy Not Possible

Querying fields that are lower than level 1 in the hierarchy is not supported by the API. For example,queries like Select Attributes.Name from Subscriber because Name is at level 2 in the hierarchy.

Server Results that Contain an Automation Object Structure Cause Exception to Be Thrown

When performing operations on an Automation object, the result of the operation causes an exception to be thrown because the response has a field that cannot be parsed by the API. To bypass this, make those types of operations asynchronous.

Was this article helpful?

💙 Thanks for your feedback!

Leave feedback…

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.