You are here:
JSON Validations
When you provide a custom JSON in an order template, the system verifies that the JSON is valid and that all required attributes are present. All attributes and attribute values are case-sensitive and the attributes must be part of the objects that they’re referred from.
See Attributes of the Custom JSON for more information on the JSON attributes.
Note While adding custom fields, make sure the API names (fieldApiName) are unique and
don’t match the API names of the Consumer Goods Cloud entities.
Apart from generic checks, here’s the list of specific checks for the individual JSON fields.
Add Items JSON
- At least one field must have isColumn as true.
- At least one field must have isFilter as true.
- The Add Item JSON must have the Type field as one of the attributes.
- The Add Item JSON must have the Unit Type field from the Unit Of Measure object as one of the attributes.
Free Items JSON
- The Free Item JSON must have at least one field from the Product object.
- All fields present must be part of the Order Items JSON as well.
- All fields from the Product object must be part of the Add Items JSON as well.
Order Items JSON
- The Order Item JSON must have the Quantity field from the Order Items object as one of the attributes.
- The Order Item JSON must have the Unit Type field from the Order Items object as one of the attributes.
- The Order Item JSON must have at least one field from the Product object.
- All fields from the Product object must be a part of the Add Items JSON as well.
- fieldType for the Data Type field must be from the list of data types (boolean, currency, date, URL, icon, number, percent, picklist, related object name).
Order Details JSON
- At least one field from an object must be present.
Order Page Header JSON
- At least one field from an object must be present.
Did this article solve your issue?
Let us know so we can improve!
