Resolved Data range - Today

Hello,
You can set today's date in Order date start filter which is under Date range drop down so you can filter your orders by today. Let me know if it helps.

Hello,

Why is the option "Since last run" not working for you?

Good evening.

tharuna it looks that the today option that you talk about returns today date for the option that you choose in the templare, by this i mean that it saves the actual date, so tomorrow when you run the import it will not be "today", so he will keep doing the day that was chosed in the template.
roland, since last run it doesn't work because it only exports the orders that are made "since last run", if the "since last run" option was directely connected to the "order status" option it would do the work, but it's not, if i choose the order status "shipped" since last run it would be easy to think that it will export the orders marked has shiped "since last run" independent of the date, but it doesn't, actually, first it checks the orders "since last run" then exports the ones marked has "shipped", i hope that i made it clear, it's a bit cofusing and my english is not that good (sorry about that).
It would be great to put one iteration that does something like this:
if "status"==true{
checkmodifieddatein(sincelastrun);
if checkmodifieddatein == true{
return orders;
}
}
something like this, sorry for the mess, i don't code anymore so the sintax is probably a nonsense but maybe you can get what i mean.

Thanks in advance.

Hello,

tharuna it looks that the today option that you talk about returns today date for the option that you choose in the templare, by this i mean that it saves the actual date, so tomorrow when you run the import it will not be "today", so he will keep doing the day that was chosed in the template.

Yes i agree that every time you run the export you may need to change this date option.

roland, since last run it doesn't work because it only exports the orders that are made "since last run", if the "since last run" option was directely connected to the "order status" option it would do the work, but it's not, if i choose the order status "shipped" since last run it would be easy to think that it will export the orders marked has shiped "since last run" independent of the date, but it doesn't, actually, first it checks the orders "since last run" then exports the ones marked has "shipped", i hope that i made it clear, it's a bit cofusing and my english is not that good (sorry about that).
It would be great to put one iteration that does something like this:
if "status"==true{
checkmodifieddatein(sincelastrun);
if checkmodifieddatein == true{
return orders;
}
}
something like this, sorry for the mess, i don't code anymore so the sintax is probably a nonsense but maybe you can get what i mean.

The problem was that CSVI has been using created_on date to check with the last run date and so even when the order has been modified, the order was not included in the export. The attached patch file will give you an option in template settings to select created_on or modified_on date to be used for checking for date range option. You can load the patch file using CSVI maintenance menu and look for field Use date field under Date range option in options tab. By default it is set to created date, set it to modified date and check if your exports works as expected.

patch_vm_order_2010_10_13.zip

Hello,

We understood your idea and support your request to make this more intelligent. Please test the patch Tharuna has provided and we can include it in a future release.