This may not be the best way to write a view in MySQL for Magento, but it\’s at least a start.

http://www.magentocommerce.com/wiki/groups/207/fedex_-_shipping_view

...I now know that the comment space is limited here… so I have created a wiki document that contains the SQL for the view I created.

This view was a bit of a mess to put together. It would seem there has to be a better way to do this, but I’m not real sure what it would be. The first query I put together I used a lot of joins, but that made the dumb thing about croack taking 10 times longer every time I added another table to join for one more attribute once I got up to 6 or 7. Here with the sub-select queries, it actually executes quickly on a database with 4 orders. I don’t know if it will have issues as the database grows though.

I probably need to have it filter the open orders or something like that so that as the database grows the view will only reference the smaller list of orders that haven’t shipped yet, instead of all orders from the beginning of time.

In the FedEx Ship Manager under the shipment details i keep getting **Unsupported Type** for all the fields except for weight & subtotal.  Any ideas would be much appreciated
Thanks in advance

I know there were a lot of warnings about the field length being too long in the mapping, but I didn’t see that affect the operation of the integration. I think that just causes it to truncate the field.

The example and testing I performed was under version v.2353-a. What version are you using?

What version of Magneto are you running on?

Is Ship Manager prompting you for a Lookup value?

Have you checked to see what the results of a query to the vi_sales_order_shipping table looks like, and if some of the fields you are expecting values have the correct values. It’s possible that Ship Manager would throw a fit if it was getting a lot of NULL values.

Also check your integration package under the Import -> Match section and under Select Index, make sure the Lookup dialog is ONLY referncing the oder_no field from the view.