Marketo 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 Marketo for more information.
Version 1.3.0
Released October 21, 2021.
New And Noteworthy
- Added Send operation functionality which is used to make API calls to the Marketo API. The Send operation supports the Request entity used to build the HTTP call to the API.
Changes In Functionality
The connector supports two Add blocks that are used in different circumstances.
-
There is an Add block that only supports the List entity. That block is used to add leads to Marketo lists.
-
The second Add block is used in conjunction with the Send block to support Hierarchical data allowing you to add multiple nested records in a single parent record. The hierarchy can extend down multiple levels, for example, a record containing a Country or parent, States or children, and Cities within each state or grandchildren.
Closed Issues
57984
If you attempt to run debug for a map with Net Change enabled for the activitydate field and no other filters, you cannot use the Query Block Preview tab to preview fields for the Activity entity. If you add a separate filter for activitydate on the Filter tab, the Preview displays correctly, however an error is generated indicating that only one filter is allowed on this field. (Case # 01722935, 62667)
56995 / 57270 / 70709
When querying the Marketo API, records are not returned in order by date. If the Net Change option is enabled on the Query Block to return only new and updated records, the Marketo Connector must request all records, sort them by date, and then locate only the new and updated records. This process takes place in memory and affects agent memory requirements. If you are using an Connect on-premise agent and the server where that agent is installed does not have enough memory, it may appear that there is a memory leak due to the volume of records being sorted. (Case # 62575)
57647 / 57730
When the ActivityID field of the Activity entity contains an ID that is too large for data type Int32, an error similar to the following is generated.(Case # 63064)
Severity: Error
Title:Scribe.Core.Processor.Executions.RunMapProcessExecutor
Win32 ThreadId:43392
Message: The process '7edfc0a3-82aa-4b44-a3af-b58c9290ce42' completed with an exception: Exception Type : OverflowException
Message : Value was either too large or too small for an Int32.
45903
Querying the Activity entity did not return required field values. (Case # 59496)
SCMKTR-9
Query block preview does not show the array of values for the Activity entity attribute field. It is now supported using the HTTP Request to the REST API.
SCMKTR-11
The Marketo connector does not support Smart Lists. They are now supported using the HTTP Request to the REST API.
SCMKTR-12
The Marketo connector does not support CreateDuplicate. It is now supported using the HTTP Request to the REST API.
Known Issues
58065
Summary: The listid field displays as NULL in the Query Block Preview Tab. This is a virtual field used for Match Criteria on Updates and Deletes and is not part of the metadata provided by the API. (Case # 62667)
Workaround: None.
33743 / 34487
Summary: Datetime fields returned by the Marketo REST API are returned as UTC, however they do not include the date type. If the datetime is used in a formula, it is converted to UTC again, which can cause datetime information to be offset. (Case # 51551)
Workaround: flow the Marketo source datetime field directly to a target datetime field without using a formula. If you need to include the datetime field in a formula, use one of the datetime functions to convert the datetime back to the correct UTC time and date. See Date Time Functions.
33553
Summary: Processing a Marketo source record that is greater than 1MB in size generates a fatal error and stops the app from executing.
Workaround: You may need to modify the source data to reduce the size of the record causing the error or use a filter to skip that record.
27688 / 28056
Summary: If you have Custom entities and you attempt to reset metadata for your Marketo REST connection, you may see an error similar to the following: (Case # 86273)
Object reference not set to an instance of an object
Workaround: This error can be generated if your Marketo account does not have permission to access custom entities. Contact Marketo for assistance in setting the correct permissions for your custom entities.
Version 1.2.1
Released June 19, 2017.
New And Noteworthy
There are no new features for this release.
Closed Issues
45923
When querying Activities, field values displayed as NULL in the Query Preview tab. (Case # 59496)
46118
In some Marketo environments, querying Leads failed with the following error: (Case # 59497)
Sequence contains more than one matching element.
Version 1.2.0
Released June 7, 2017.
New And Noteworthy
- Added support for the following:
- marketoGUID field for Activity and Activity Types entities. (43181)
- Company entity with Query, Create, Update, Delete, and Upsert operations. (40578, 40590, 40825, 42875, 42876)
- SalesPerson entity with Query, Create, Update, Delete, and Upsert operations. (40664, 40667, 40828, 42900, 42878)
- Lookup operation for the Company and Salesperson entities. (43341)
- Create and Update operations for the Lead entity. (42879, 42880)
- Query and Create operations on Custom Activities entities and associating them with Leads. (42877)
- Enhanced the Upsert operation for leads to use the virtual field, ExternalIDFieldName, to indicate which field should be used as Match Criteria when upserting Lead data. (42908)
Closed Issues
32875 / 34019
Updates to Marketo datetime fields were off by 12 hours. (Case # 89155)
32876 / 34021 / 43679
When a flow attempted to process records for an entity with a large number of fields, a Fatal Error was generated and the flow stopped executing. (Case # 89253)
42717 / 43295
When querying an entity that has a large number of fields, the fields were included in the request URL causing the following error to be generated: (Case # 57818)
Exception Type : InvalidExecuteQueryException Message : The following error has occurred in the Marketo Connector: An error occurred while sending the request.
March 2016 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
11986 /15498
The Add block used to add a Lead to a List was not updating the List correctly when the List name was used in the ListKeyValue field. (Case # 79621)
15497
The leadScore field on the Lead entity was missing from the Query block. (Case # 80403 )
December 22, 2015 Release
New And Noteworthy
The following entities are currently supported by this Connector:
- Activity
- Activity Types
- Lead
- List
- Opportunity
- OpportunityRole
- Custom Objects
Closed Issues
There are no closed issues in this release.