intnull
Forum Replies Created
-
OK, I have found a solution to my row output. I changed how I was filtering from directly on the products to a new custom field. That seems to have resolved my issue.
I will close this now. Thank you so much again Alex. You are the best supported plugin on here.
I had that ticked but your code removed them from the file. THANK YOU. now I just need to figure out why my orders stop exporting past the 7th of September.
I have a theory. Is it possible that if someone modified the product data for the products I am filtering by that it would actually not recognise them as the same thing anymore? I seem to remember the store changed product details on that date.
Not, I don’t have either ticked
My apologies. The orders are actually fine. I have 3 rows which are simply not showing any details in the export but are at a mixture of correct statuses and I can access them through the front end. I think the problem actually seems to be with the export.
The status for them are two completed and 1 printed which are in my search criteria and expected. The problem is with the store’s operations, they were refunded and then bulk updated back to a completed status. I guess the product data is obliterated upon refund or something.
However, is there a way to confirm and remove rows with blanks at run time? The other end of this integration is fragile (unfortunately) and I have to protect against them getting blank rows, not just hope the orders are always going to be healthy.
I also still don’t understand why I am not seeing the newer orders.
Thanks for how amazingly speedy your responses are
Hi Alex I will check the statuses but I just noticed it is almost as though it is caching the search. I noticed it is also not exporting any more or less rows than it did the first time I exported it. There are definitely new orders since the first time. It is a scheduled job I am testing btw. I have tried setting the “This Year” and Since last run etc. Could it be caching the row IDs? Perhaps why my status filters are not effecting the deleted rows.
Just spotted a JS error, it was caused by another plug-in which clearly didn’t like the WC update. Oh the joys of this extremely fragile eco-system
Haha, now I feel silly, I was too fixated on the file type selection to notice it was updating the file name field.