Is there an option to be able to lift Orders out of the back office as a CSV?
I'm sure I've seen this done before in Tea Commerce?
Would be good to lift the details out so that a customer can import them into their accounting software easily, and maybe lift the emails for marketing campaigns?
Is it a case of adding a button and a controller and doing this manually?
...which contains a few files you can drop into your solution. This includes a new user control, but also, an updated SearchOrders.aspx file which replaces the one that comes with TC. This adds a new control in there to export orders between a given set of dates.
Just as a slight warning, this zip file was created a while ago, so you may want to do a diff on the SearchOrders.aspx file and merge over the inclusion of the new user control, rather than just outright replacing that aspx file as I can't be sure that file hasn't changed since this zip file was created.
Also, because you are editing a core TC file, it's worth knowing if you do perform an upgrade, that file is likely to get "updated", so be sure to keep a backup of the modified one and re-merge it in after any upgrade.
Tea Commerce - Order export CSV
Hi
Is there an option to be able to lift Orders out of the back office as a CSV? I'm sure I've seen this done before in Tea Commerce?
Would be good to lift the details out so that a customer can import them into their accounting software easily, and maybe lift the emails for marketing campaigns?
Is it a case of adding a button and a controller and doing this manually?
Hey Neil,
It is possible, but it's not that ideal how it's achieved. You can find a zip file here...
...which contains a few files you can drop into your solution. This includes a new user control, but also, an updated
SearchOrders.aspxfile which replaces the one that comes with TC. This adds a new control in there to export orders between a given set of dates.Just as a slight warning, this zip file was created a while ago, so you may want to do a diff on the
SearchOrders.aspxfile and merge over the inclusion of the new user control, rather than just outright replacing that aspx file as I can't be sure that file hasn't changed since this zip file was created.Also, because you are editing a core TC file, it's worth knowing if you do perform an upgrade, that file is likely to get "updated", so be sure to keep a backup of the modified one and re-merge it in after any upgrade.
Like I said, not ideal, but it does work.
Matt
Thanks, Matt, thought I'd seen this somewhere.
Works a treat, thank you!!
is working on a reply...