Shipment exporting strategy question (3 replies)
One way might be a compromise that your client could accept. Create a table in a different database. In that table you can write the key fields of your shipment transaction.
Add a trigger to that table to update the OEORDDO table in the Sage database. That way you are updating the record that you want and you're not getting direct access to the Sage database and your speed would be quick.
Alternatively you might be able to update another view within Sage, like an optional field table (I haven't checked). You can add a shipment record to the optional field table and, again, use a trigger to update the related OEORDDO table.
Randy, the reason you want to have direct database access in this case, is to do with Sage300.
When a shipment is invoiced it becomes un-editable, so you would not be able to set this value.
The connector does support updating Shipments, so you can always try updating via the connector.
Closed due to inactivity.
After creating shipments in Magento from Sage data, we write the "exported status" to Sage so we know to not process the data again.
The strategy we currently use utilizes a DB writer to write back directly to the OEORDDO (order detail optional field table) table.
We have a client who prefers that we do not have direct DB access. Is it possible to update the Order Detail optional fields using the Sage 300 connector?