Portal Community
Only listed fields survive In default (rule-based) mode, Data Mapping builds a brand-new output object containing only the fields listed in dataMappings. Anything not explicitly listed is silently dropped — nothing is auto-carried through. (dataMappingMode: "passthrough" copies the whole record verbatim instead, but then none of your renames/transforms apply — it's all-or-nothing.) That's why the mapping below lists every field from the product record, not just the ones being renamed.

Configuration

dataMappingMode: left on default (rule-based mapping).

Data Mapping configuration showing dataMappings JSON
"Standardize data" — the Data Mappings JSON editor, matching the table below.
sourceFieldtargetFieldtransform
idproductId
titleproductNameuppercase
descriptiondescription
categorycategory
priceprice
discountPercentagediscountPercent
ratingrating
stockinStockQty
tagstags
brandbrand
skusku
weightweight
dimensionsdimensions
warrantyInformationwarrantyInformation
shippingInformationshippingInformation
availabilityStatusavailabilityStatus
reviewsreviews
returnPolicyreturnPolicy
minimumOrderQuantityminimumOrderQuantity
metameta
imagesimages
thumbnailthumbnail
category (reused)summaryexpression: item.category + ': ' + item.title

The last row reuses category as the source for a derived field (summary) — a rule's sourceField doesn't have to be unique across rules.

Before / After — Product 1

Before:

{ "id": 1, "title": "Essence Mascara Lash Princess", "discountPercentage": 10.48, "stock": 99, "category": "beauty" }

After:

{
  "productId": 1,
  "productName": "ESSENCE MASCARA LASH PRINCESS",
  "discountPercent": 10.48,
  "inStockQty": 99,
  "category": "beauty",
  "summary": "beauty: Essence Mascara Lash Princess",
  "...": "...(every other field carried through under its original name)"
}