The ingestManagedAttributeValues operation has success and failure responses.
<ingest:ingestManagedAttributeValuesResponse xmlns:ingest="http://www.endeca.com/MDEX/ingest/2/0"> <ingest:numManagedAttributesCreated>1</ingest:numManagedAttributesCreated> <ingest:numManagedAttributeValuesCreated>3</ingest:numManagedAttributeValuesCreated> </ingest:ingestManagedAttributeValuesResponse>
In the sample response, the numManagedAttributesCreated element shows that one managed attribute was created, while the numManagedAttributeValuesCreated element shows that three managed values were created.
On failure, a SOAP fault is returned. The ingest:ingestFault and ingest:errorDetail elements should contain the error that caused the failure.
<ns:ingestManagedAttributeValues> <ns:managedAttributeValue displayName="bicycle saddles" spec="Saddle" parentSpec="Parts" managedAttribute="Component"> </ns:managedAttributeValue> </ns:ingestManagedAttributeValues>
<ingest:errorDetail> Error applying updates: Managed attribute value put refers to parent spec "Parts", which does not exist in managed attribute "Component" </ingest:errorDetail>
In this example, the reason for the error is that the request refers to a non-existent parent managed value (58 in the example).