Michael, we will need to check this out.

Do you have a link to the extension?

Here is the link:   http://codecanyon.net/item/magento-order-attributes/8487808

Thanks

Michael, we've had various luck with extension developers (some work, some do not).

The question which needs to be asked is whether the attributes added by the extension will be available through the "order.info" API call.

We did have a client where they were using the Amasty Order Attributes plugin (https://amasty.com/order-attributes.html), and at the time, the attributes were not exposed through the API (not sure if this is still the case).

The "ordershipswhenready" field does come through in a sales orders.info API call  (see attached sample API result).

The extension we're using creates a "custom" array with key/value pairs for each attribute (the section below is the last part of the response). Does this help?

{

"parent_id": "41",

"is_customer_notified": "1",

"is_visible_on_front": "0",

"comment": null,

"status": "pending",

"created_at": "2015-04-10 02:41:21",

"entity_name": "order",

"store_id": "1"

}

],

"custom": [

{

"key": "ordershipswhenready",

"value": "25"

}

]

}

Is the data above compatible with the Magento Order Reader?  If so, is there a mistake in the way I am inputting the field name in the reader?  Let me know if you'd like for me to provide anything else.

-Thanks

Michael, the problem lies in the way the data is being exposed. The connector works by scanning for key/value pairs such as the fields: parent_id, comment, status, etc.

Because the fields are nested into a custom array where each object has separate key and value properties it means with the current connector we're unable to access the data unless we jump through a lot of hoops. If we were comparing the two methods of access the values of say the store_id field to the ordershipswhenready custom property they would look like:

/store_id

vs.

/custom[0]/value[key='ordershipswhenready']

Very different.

Not sure which of the extension plugins expose the way we need.

Thanks, I have gone back to the developers for next steps.  As long as the new fields are listed in the same array as the parent_id, comment, status, etc. then they will be able to be referenced in the Magento Connector "Custom Header Field List"?  It will be a great help if you would be able to find a recommended extension to use with the customer header field list option in the connector.

The Magento developers say this is the standard behavior for order attributes in Magento, and that they would need to do custom development to have them display in the array with the common fields.  A recommended extension for order attributes will be VERY helpful.  Thank you!

If the issue still exists, then I would recommend to use this FME Additional Checkout Fields extension having tons of features to add custom order fields and read/save the data inserted in the custom fields. 

Check this: Magento Order Attributes

If you need any customization, then contact the FME support team.

Shared replies are really very helpful. Its help me a lot.  https://www.magentocommerce.com/magento-connect/advance-product-designer.html