I don’t think it fails with the FedEx Web Services (WS). I’d have to check but I remember seeing errors when it’s over 35.
Time for an Epicor problem! 
2 Likes
@spaceage do you do FexEx LTL too or just small pack?
Just small pack
1 Like
Did you end up putting in the ticket? I have time now booked with my users to test it out next week. I’ll go through all the phone number, company names, etc. and see if it works.
1 Like
There are a number of properties in the Fedex OpenAPI specification where there is a maximum length listed in the description but have no maxLength property defined. Here’s one example of this:
"companyName": {
"type": "string",
"description": "The shipper's company name. Max length is 35.<br>Example: FedEx",
"example": "Fedex"
}
So Fedex returns this error when attempting to freight a shipment with a customer name longer than 35 characters (which is undocumented, as far I can tell):
Another case of busted API specs (sigh).
1 Like
Our testing so far is good for both small pack and LTL. Our shipping manager is out next week so we’re holding off until the week of the 16th to do the change.
1 Like
@dmmory, I was also reading different posts about their API and from what I read I think there’s an option to truncate it, but I can’t tell if that’s on Fedex’s side or what.
Were you able to ship FedEx LTL from Customer Shipment Entry? We have been unable to ship LTL in our tests, and I was informed by the QuickShip help desk that two fields are missing that Epicor would need to patch in order for this to work, specifically, the contact name and company name for the billing account on the customer record.
3 Likes
We don’t usually ship “third party” billing type. “FedEx Recipient” worked and we haven’t tested it yet so good find!
Edit: I checked our DB and we do FedEx LTL mostly via Shipper but also FedEx Recipient and FedEx PrePaid only. Never have we shipping “Third Party”
1 Like
it will fail if the customer notes have to many characters. just had one 1051 characters the limit is 1000.
returnStatus": “Error”,
“returnMessage”: “An error occurred while saving the entity changes. See the inner exception for details. - String or binary data would be truncated.”,
“shipmentNumber”: “0”,
“totalFreightCharges”: 0.0,
“totalBilledFreightCharges”: 0.0
Found this out by looking at the freight XML’s
1 Like
Also had a contact that was more than 35 characters that failed.
1 Like
if you have a partially shipped order with too many characters in the company name you cannot ship any more lines on the order unless shipping knows to modify the customer on the packid
The order itself will not allow the change.
1 Like
That looks like a QuickShip error.
The CustomerNotes column in the Shipping table in Quickship is nvarchar(1000), so you would get that error regardless of the carrier that is used.
It must have occurred with the latest release of QS then; we have been shipping to this customer every week for the past 40 years. Granted the notes may have been updated within that time frame, so cannot say for sure that someone since added more notes.
2 Likes
FedEx and I believe UPS max the lines to 35 chars. Should truncate instead of erroring though…
1 Like
Agreed
That’s the thing Randy, if you could open a case with epiccare and ask them to do that, that would be helpful.
I entered one yesterday and I heard from a familiar face at QS that said they’d look into it.
If we get more people asking for the option to truncate that could help speed it along. And I’d like to suggest we have them create it retroactively so we can add something as an option to the Fedex service in QS, much like we did when UPS started OAuth… just add an option in quick ship… not have to upgrade or anything like that.
Thanks dad, but I have had a case open about FedEx REST issues. 
1 Like
Epicor is going to have to act fast. The FedEx deadline is coming fast.
2 Likes
So far ground has remained the same besides the 35 character limit company name.
The phone number thing can be mitigated by setting up a default phone in quick ship FYI.
1 Like