Filtering
-
To use your filters in REST API payloads, you need to edit them in Campaign v8 and provide a name to use in your payloads. To do so access the filter’s additional parameters from the Parameters tab, and provide the desired name in the Filter name in REST API field.
-
The “by” prefix required to use custom filters is no longer needed. The filter name should be used as-is in your requests.
Example:
GET https://mc.adobe.io/<ORGANIZATION>/campaign/profileAndServicesExt/<resourceName>/<customFilterName>?<customFilterparam>=<customFilterValue>
Dropped database fields
Some fields from the database are being dropped during migration. When using a dropped field, REST APIs will return blank values. In the future, all dropped fields will be deprecated and removed.
POST with linked resources
When using the following request body format, with “vehicleOwner” representing the link to “nms:recipient”:
{
"vehicleNumber": "20009",
"vehicleName": "Model E",
"vehicleOwner":{
"firstName":"tester 11",
"lastName":"Smith 11"
}
}
The link information is ignored. Consequently, a new record is generated under “cusVehicle” containing only “vehicleNumber” and “vehicleName” values. However, the link remains null, resulting in “vehicleOwner” being set to null.
In Campaign v8, when the same request body structure is used and the “vehicle” is linked to a profile, an error occurs. This error occurs because the “firstName” property is not recognized as valid for “cusVehicle.”. However, a request body comprising only the attributes without the link functions without any issues.