The challenge was how to extract this information, given that the.
Aside from “normal” file attributes such as date modified and size, the Windows Explorer (shell) provides extended file property information which can be quite valuable.
We will need to define the fields that are needed for export, the type of parameters of the filter, the format of the file, and the column header names, if any.Over the weekend, I decided to try and import image metadata using C# and the. The parameters for the job are defined before kicking off the export using the Create Export Lead Job endpoint. The exported file will be rendered as a comma-separated values, tab-separated values, or space-separated values file, respectively if set. The value will be the name of the exported column header for that field.Īccepts one of: CSV, TSV, SSV. This is the API name of the field which can be retrieved by calling Describe Lead. The key must be the name of a field included in the export job. You can specify the “ecids” field to include ECIDs in the export file.Ī JSON object containing key-value pairs of field and column header names. Note: When the Adobe Experience Cloud Audience Sharing feature is enabled, a cookie sync process occurs that associates Adobe Experience Cloud ID (ECID) with Marketo leads. The column header for each field will be the REST API name of each field, unless overridden with columnHeader. The listed fields will be included in the exported file. Each string must be the REST API name of a Marketo lead field. The fields parameter accepts a JSON array of strings. The Create Export Lead Job endpoint provides several formatting options, giving the user the ability to include particular fields within the exported file, the ability to rename column headers of these fields, and the format of the exported file. Customers may contact Marketo Support to have this functionality enabled in their subscription.
If unavailable for your subscription, you will receive an error when calling the Create Export Lead Job endpoint (“1035, Unsupported filter type for target subscription”). * Filter type is unavailable for some subscriptions. Retrieve smart list ids using the Get Smart Lists endpoint. Jobs with this filter type will return all accessible records which are members of the smart lists at the time that the job begins processing. Retrieve smart list names using the Get Smart Lists endpoint.Īccepts the id of a smart list. Retrieve static list ids using the Get Lists endpoint.Īccepts the name of a smart list. Jobs with this filter type will return all accessible records which are members of the static list at the time that the job begins processing. Retrieve static list names using the Get Lists endpoint.Īccepts the id of a static list. Jobs with this filter type will return all accessible records which are members of the static list at the time that the job begins processing. Jobs with this filter type will return all accessible records which were most recently updated within the date range.Īccepts the name of a static list. It filters based on leads which had Data Value Change records in the given timeframe. Note: This filter does not filter on the “updatedAt” field which only reflects updates to standard fields. Jobs with this filter type will return all accessible records which were created within the date range. Datetimes should be in an ISO-8601 format, without milliseconds. startAt accepts a datetime representing the low-watermark, and endAt accepts a datetime representing the high-watermark. Filter TypeĪccepts a JSON object with the members startAt and endAt. Only one filter type may be specified per export job. Certain filters, including the updatedAt, smartListName, and smartListId require additional infrastructure components which have not yet been rolled out to all subscriptions. Leads support a variety of filter options. The Bulk Lead Extract APIs require that the owning API user have a role with one or both of the Read-Only Lead, or Read-Write Lead permissions.