To update product's transaction data, mention the following in the postman and then click Send.
POST
Query Params |
|
---|---|
Key | Value |
CompanyId | 0642243f-73e6-4f04-9037-a118112c2e99 |
VocabularyId | 0642243f-73e6-4f04-9037-a118112c2e99 |
Headers
Authorization: Specify required Auth Token in the header.
Request
{
"TransactionImportData": { //Denotes we are sending Transactions in this object
"TransactionsToImport": [ //Contains the array of transactions being sent to CXH
{
"ImportMode": "Create", //Same options as Products; "Create", "Update", "CreateOrUpdate" "TargetParty": "TargetPartyA", //Transaction can only target one Recipient, which also is not necessarily a recipient. Can be mapped or the GUID directly.
"TransactionIdentifierPropertyOverride": "UPC", //Allows for override of the overall transaction identifier for this specific transaction
"TransactionIdentifierValue": "5324579", //The identifier that will be used for matching logic
"TransactionType": "Shipment", //This effectively maps to a specific requirement set; whcih can be done with the ID or with a mapping
"ProductReferencePropertyOverride": "MFG Part #", //Transactions may directly reference Product Rec rds; this allows an override of the property used to create that reference
"ProductInstanceReferencePropertyOverride": "Product Instance Reference Property Override", //Transactions may reference product instances, this allows for override of the property used to create that reference
"Values": [ //Transactions can house information on the "Header" of the transaction; these are Attributes just like Products house data
{
"Name": "Shipment_Date",
"ValuesByLocale": {
"": "1/10/2021"
}
}
],
"ContainerValues": [
{
"ParentAttribute": "ProductInstancesReferences",
//The below is an example of how transactions m ake a reference to Product Instances
// if Product Instances are being leveraged
"RowList": [
{
"Values": [
{
"Name": "ProductInstanceReferenceAttribute",
"ValuesByLocale": {
"": {
"Type": "OwnedData", //This "OwnedData" object allows us to leverage multipart keys when creating these references
"Reference": { //So in the below case, I'm looking for a Product Instance that fits both the b elow criteria in an "And" clause
"ProductInstance": [
{
"Alias": "SERIAL_NUMBER",
"Value": "CSN1"
}
],
"Product": [
{
"Alias": "GTIN",
"Value": "195278033105"
}
]
}
}
}
}
]
},
{
"ParentAttribute": "ProductReferences",
//And example of what it looks like when a transaction directly references a
// Product record. Which could include some "Transaction Specific" data as well
"RowList": [
{
"Values": [
{
"Name": "ProductReferenceAttribute",
"ValuesByLocale": {
"": "63052530752521"
}
},
{
"Name": "MFG_DATE",
"ValuesByLocale": {
"": "7/10/2020"
}
}
]
}
]
}
]
}
]
}
],
"TransactionIdentifierProperty": "ShipmentId", //The attribute that will be the overall identifier for the transacti on, if no override present. Can be GUID or mapped.
"ProductReferenceProperty": "GTIN", //The attribute that will be leveraged for Product References, if no override present. Can be GUID or mapped.
"ProductInstanceReferenceProperty": "SERIAL_NUMBER" //The attribute that will be used for Product Instan ce references, if no override present. Can be GUID or mapped.
},
"ErrorMode": "Fail" //Just like products, can be "Fail" or "Ignore"
}
Response 200 OK
Need to be added.