TI-API: customerLineItemNumber and tiLineItemNumber are missing

Hi Petr,

This has already reported, and we are preparing to roll out a fix in the next release (waiting to get a date).  I have tagged this thread and will let you know once the fix is in production.    Thank you!

Regards,

Faye

Now is in GET response the tiLineItemNumber (a different number than in the creation response) but then customerLineItemNumber is still missing.

	"lineItems": [{
		"tiLineItemNumber": "000010",
		"tiPartNumber": "TPS3895ADRYR",
		"tiPartDescription": "Single-channel, ultra-small, adjustable supervisor with active-high, push-pull output",
		"customerPartNumber": "TPS3895ADRYR",
		"customReelIndicator": false,
		"partType": "IC",
		"htsCode": "8542399000",
		"cooCode": "TH",
		"eccn": "EAR99",
		"batchCode": "2147488UT2",
		"status": "Complete",
		"quantity": 30,
		"shippedQuantity": 30,
		"unitPrice": 0.652,
		"netPrice": 19.560,
		"packageInformation": {
			"carrier": "LARGE T&R",
			"delivery": [{
				"type": "Cut tape"
			}]
		},
		"waiverAvailable": false,
		"trackingAndShipping": {
			"creditMemo": [{
				"multiShipFlag": false
			}],
			"invoices": [...],
			"shippingFreightAccount": "TI",
			"trackingNumbers": [...]
		},
		"customerReferenceNum": "TPS3895ADRYR"
	}

Petr,

The resolution to this problem has not been release in the production environment yet.   At present, the target is around 2 - 3 weeks.  If we can get the changes in production sooner, I will let you know.

Regards,

Faye

Hello, I tried putting our number in customerItemComments too, but this item is not returned either when creating order or when checking the order status. Is this item included in the planned fix or should I make a new thread?

Order reqeust:

"lineItems": [{
			"customerLineItemNumber": 3,
			"tiPartNumber": "TS3A24157DGSR",
			"customerPartNumber": "TS3A24157DGSR_S",
			"customReelIndicator": false,
			"quantity": 1000,
			"customerItemComments": [{
				"message": "my lineNumber:3"
			}]
		},...

Order response (customerItemComments is null):

"lineItems": [{
			"tiLineItemNumber": "0",
			"customerLineItemNumber": "3",
			"tiPartNumber": "TS3A24157DGSR",
			"customerPartNumber": "TS3A24157DGSR_S",
			"tiPartDescription": "0.65-Ω on-state resistance, 3.3-V, 2:1 (SPDT), 2-channel analog switch",
			"partType": "IC",
			"htsCode": "",
			"coCode": "",
			"quantity": 1000,
			"shippedQuantity": 0,
			"unitPrice": 0.304,
			"netPrice": 304.0,
			"dateCode": null,
			"batchCode": null,
			"status": "PROCESSING",
			"fees": null,
			"discounts": null,
			"packageInformation": {
				"carrier": "LARGE T&R",
				"delivery": [{
					"type": "Cut tape",
					"quantity": 1000
				}]
			},
			"waiverAvailable": "false",
			"trackingAndShipping": [{
				"shippingFreightAccount": "TI",
				"trackingNumbers": [{
					"shippingFromCountryCode": "Shenzhen",
					"serviceLevel": "International priority",
					"shipDate": null,
					"masterTracking": null,
					"leg1Carrier": null,
					"leg1Tracking": null,
					"leg1TrackingURL": null,
					"leg2Carrier": null,
					"leg2Tracking": null,
					"leg2TrackingURL": null
				}],
				"invoices": [],
				"creditMemo": null
			}],
			"customerItemComments": null,
			"notifications": []
		},...

Order status response (customerItemComments is missing):

"lineItems": [{
		"tiLineItemNumber": "000010",
		"tiPartNumber": "TS3A24157DGSR",
		"tiPartDescription": "0.65-Ω on-state resistance, 3.3-V, 2:1 (SPDT), 2-channel analog switch",
		"customerPartNumber": "TS3A24157DGSR_S",
		"customReelIndicator": false,
		"partType": "IC",
		"htsCode": "8542399000",
		"eccn": "EAR99",
		"status": "Created",
		"quantity": 1000,
		"shippedQuantity": 0,
		"unitPrice": 0.304,
		"netPrice": 304.000,
		"packageInformation": {
			"carrier": "LARGE T&R",
			"delivery": [{
				"type": "Cut tape"
			}]
		},
		"waiverAvailable": false,
		"trackingAndShipping": {
			"creditMemo": [{
				"multiShipFlag": false
			}],
			"shippingFreightAccount": "TI",
			"trackingNumbers": [{
				"shippingFromCountryCode": "CN"
			}]
		},
		"customerReferenceNum": "TS3A24157DGSR_S"
	},..

Petr,

Wow!  You are on a roll! 

First, we have released a fix so that the "customerLineItemNumber" will now show up when you use the GET order API.  We have one minor issue we need to resolve associated with the tiLineItemNumber sequencing, but, hopefully this does not impact you.  Once we resolve this, I'll let you know. 

Secondly, I'll look into this new item.   Looks like the problem starts when the order response is returned, so, I need to confirm that we're storing this and then see what both APIs are suppose to return (or if this is the planned behavior).

Regards,

Faye

Faye Rainey said:

First, we have released a fix so that the "customerLineItemNumber" will now show up when you use the GET order API.

Item customerLineItemNumber does now return, but it has a bad value in GET response. That was a better state before it didn't come back.

POST request:

"lineItems": [{
			"customerLineItemNumber": 5,
			"tiPartNumber": "TPS7A8701RTJT",
			"customerPartNumber": "TPS7A87_S",
			"customReelIndicator": false,
			"quantity": 500,
			"customerItemComments": [{
				"message": "my lineNumber:5"
			}]
		}]

POST response:

		"lineItems": [{
			"tiLineItemNumber": "0",
			"customerLineItemNumber": "5",
			"tiPartNumber": "TPS7A8701RTJT",
			"customerPartNumber": "TPS7A87_S",
			"tiPartDescription": "500-mA, low-noise, high-PSRR, dual-channel adjustable ultra-low-dropout voltage regulator",
			"partType": "IC",
			"htsCode": "",
			"coCode": "",
			"quantity": 500,
			"shippedQuantity": 0,
			"unitPrice": 1.053,
			"netPrice": 526.5,
			"dateCode": null,
			"batchCode": null,
			"status": "PROCESSING",
			"fees": null,
			"discounts": null,
			"packageInformation": {
				"carrier": "SMALL T&R",
				"delivery": [{
					"type": "Full reel",
					"quantity": 500
				}]
			},
			"waiverAvailable": "false",
			"trackingAndShipping": [{
				"shippingFreightAccount": "TI",
				"trackingNumbers": [{
					"shippingFromCountryCode": "Shanghai",
					"serviceLevel": "International priority",
					"shipDate": null,
					"masterTracking": null,
					"leg1Carrier": null,
					"leg1Tracking": null,
					"leg1TrackingURL": null,
					"leg2Carrier": null,
					"leg2Tracking": null,
					"leg2TrackingURL": null
				}],
				"invoices": [],
				"creditMemo": null
			}],
			"customerItemComments": null,
			"notifications": []
		}],

GET response:

"lineItems": [{
		"tiLineItemNumber": "000010",
		"customerLineItemNumber": "1",
		"tiPartNumber": "TPS7A8701RTJT",
		"tiPartDescription": "500-mA, low-noise, high-PSRR, dual-channel adjustable ultra-low-dropout voltage regulator",
		"customerPartNumber": "TPS7A87_S",
		"customReelIndicator": false,
		"partType": "IC",
		"eccn": "EAR99",
		"status": "Created",
		"quantity": 500,
		"shippedQuantity": 0,
		"unitPrice": 1.053,
		"netPrice": 526.500,
		"packageInformation": {
			"carrier": "SMALL T&R",
			"delivery": [{
				"type": "Full reel x 2",
				"quantity": 500
			}]
		},
		"waiverAvailable": false,
		"trackingAndShipping": {
			"creditMemo": [],
			"invoices": [],
			"trackingNumbers": []
		},
		"customerReferenceNum": "TPS7A87_S"
	}],

Petr,

As stated in another thread you posted:

- the "customerLineItemNumber" is now showing, but it was converted from a number to a string, due to some backend processing.

- the "tiLineItemNumber" numbering sequence is incorrect and that is being worked on now.   I will inform you once we have a fix for this.

Hello Faye,

please check value of "customerLineItemNumber" in my previous post. In first and second JSON is value "5", but in GET response is "1".

Regards,

Petr

Petr,

Let me look at the logs and respond later today.

Faye

Petr,

This is an issue and I've submitted a ticket for this.  I will let you know when I get a date for a production release.  I will keep this thread open until then.  Thanks for catching this!

Regards,

Faye

Petr,

I just re-validated the problem and have escalated it.   Just to be clear...

- Order-Create "RESPONSE" returns the comments successfully

- GET /store/orders/{orderNumber} is NOT retrieving any comments.

I will keep you this open and keep you posted.

Regards,

Faye

Yes, it looks like both the order comments and item comments are returned when ordering by POST.

In GET /store/orders/{orderNumber} is new problem detected with missing order comments.

For completeness, I repeat the all reported bugs by me and not fixed in GET /store/orders/{orderNumber}

• In the "tiLineItemNumber" is not same value as in POST JSON response.
• In the "customerLineItemNumber" is not same value as in POST request and returned JSON (If the order of the items does not match the customer number).
• Item comments are missing.
• Order comments are missing (new).
• The schema in the documentation does not match the example there and the actual returned data.

Petr,

Just wanted to close on this one.   "tiLineItemNumber" and ."customerLineItemNumber" should be showing in your JSON payloads.  Also note that since the  "tiLineItemNumber" is auto generated by TI, it may not match the  "customerLineItemNumber".  Let us know if you have any additional questions.