Data Mapper Clear Cache (POST)

Clear the execution cache for the specified data mappers.

When using the Data Mapper (DM) Connect API, HTTP callouts cannot be executed in the same transaction. This is because these APIs perform an implicit DML operation through the underlying Connect API framework. If a callout is required, it must be executed in a separate transaction, for example by using an asynchronous mechanism such as @future.

Note

Resource

1/connect/omni-global/data-mapper/actions/clear-cache

Available version

64.0

HTTP methods

POST

Request body for POST

JSON example

This is a sample example to clear the execution cache by using only the name of the data mapper.

1{
2  "cacheStorageType": "Metadata",
3  "dataMapperList": {
4    "dataMappers": [
5      {
6        "dataMapperName": "DRWithLoad"
7      }
8    ]
9  }
10}

This is a sample example to clear the execution cache by using the name of the data mapper along with additional inputs.

1{
2  "cacheStorageType": "Session",
3  "dataMapperList": {
4    "dataMappers": [
5      {
6        "dataMapperName": "DRWithLoad",
7        "input": {
8          "Name": "Get Account Details"
9        }
10      }
11    ]
12  }
13}

Properties

Name	Type	Description	Required or Optional	Available Version
`cacheStorageType`	String	Storage type that's used for caching the data. Valid values are: `Session`—Cache is stored in the current user session. `Org`—Cache is shared across the entire organization. `All`—Refers to both session and org-level cache.	Required	64.0
`dataMapperList`	Data Mapper Details[]	List of data mappers to clear the cache for.	Required	64.0

Response body for POST

Data Mapper Cache Details

Public Sector Solutions Developer Guide

Data Mapper Clear Cache (POST)