Attaches a compound attribute definition together with all of its sub-attributes in one call; sub-attributes the
category already has are left untouched. No value and no flags are set here - set each sub-attribute afterwards
with the operation matching its type: PATCH /catalogs/nodes/{id}/attributes/{attributeDefinitionId} for the
simple types, and the /column, /matrix or /dictionary/values variants of that path for the rest. Handles
compound definitions only and fails when the category already has this definition as a CLA. An attribute
inherited from a parent category does not count as assigned here, so the call succeeds and creates an assignment
on this category that overrides the inherited one.
This operation takes no forceCla, because a compound attribute carries no value of its own, and
PATCH /catalogs/nodes/{id}/attributes/{attributeDefinitionId} rejects forceCla for a compound definition -
send it on the individual sub-attributes instead.
The attributes are stored on the category immediately, while adding them to products runs as a background task.
That task covers the products in this category; the products in its sub-categories are reached only once
propagation is switched on for the attribute, which is off on a newly created CLA. The task ID is returned in
the Resource-Id response header and Location points at GET /async/status/{taskId}, which reports whether
the propagation has finished.
For more detailed information on how to work with Category Level Attributes in Bluestone PIM, refer to our help
pages Category Level Attributes (CLA).
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
202Accepted
The request has been accepted for processing, but the processing has not been completed.
