I am running into the same error as this closed issue mentions.

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '.views_data_export_index_x' doesn't exist: SELECT COUNT(*) FROM {views_data_export_index_x}; Array ( ) in views_data_export_plugin_display_export->execute_initial() (line 301 of ..\plugins\views_data_export_plugin_display_export.inc).

I have not applied the patch from #14 here but this same error is mentioned in #18 and #24.

On my site I'm trying to manipulate exposed filters in a view with an export using hook_views_query_alter, so I'm fairly certain that is related to this error. The filters work fine on the in-browser rendering of the view, but upon attempting a CSV export I get the above error. Any help is greatly appreciated, and thanks in advance!

Comments

possiBri created an issue. See original summary.

augusto182’s picture

augusto182 commented

Same problem.

Traying to add "group by" using views query alter.

steven jones’s picture

steven jones commented
Status: Active » Closed (won't fix)

Sorry for the lack of attention to your issue, please accept my apologies.

Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.

As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on #3492246: Close down Drupal 7 issues.

If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)