Table field_data_commerce_vat_number doesn't exist. [#2000742]

I updated to the latest -dev from 7.x-beta1 and ran the 7001 update. When I went to the field configuration form I checked the "Soft validation" option. I got a PDO exception upon saving the form and now I keep getting it on the field settings form.

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'db.field_data_commerce_vat_number' doesn't exist: SELECT COUNT(*) AS expression FROM (SELECT 1 AS expression FROM {field_data_commerce_vat_number} field_data_commerce_vat_number0 WHERE (field_data_commerce_vat_number0.deleted = :db_condition_placeholder_0) LIMIT 1 OFFSET 0) subquery; Array ( [:db_condition_placeholder_0] => 0 ) in field_sql_storage_field_storage_query() (line 582 of modules/field/modules/field_sql_storage/field_sql_storage.module).

Comment	File	Size	Author
#8	Add new field.png	5.96 KB	roball
#6	customer-profile_-_billing_-_fields.png	39.06 KB	roball

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

dwkitchen CreditAttribution: dwkitchen commented 24 May 2013 at 18:17

Status:

Active

» Postponed (maintainer needs more info)

Does the table exist in your DB

Comment #2

a.ross CreditAttribution: a.ross commented 25 May 2013 at 06:46

Clearly it doesn't. I think you should be able to reproduce this by installing beta1 and then updating to the Dev. I was also using VAT reverse charge not sure if it's reproducible without it though.

Comment #3

a.ross CreditAttribution: a.ross commented 27 August 2013 at 14:43

Status:

Postponed (maintainer needs more info)

» Active

Erm, you released a new version (rc) without resolving this. Have you tried to actually reproduce this issue, and if so, did you figure out a way to fix it?

The vat_number_update_7001() function does not work properly.

Comment #4

roball CreditAttribution: roball commented 29 August 2013 at 15:34

Uninstalling the module and installing a fresh 7.x-1.0-rc1 should give no problems.

Comment #5

a.ross CreditAttribution: a.ross commented 29 August 2013 at 16:04

I tried that and it didn't work. That may however be due to the commerce_vat module, I haven't tested without AFAIR.

Anyway, it's not really a solution at all because this issue is in fact about the migration path being broken.

Comment #6

roball CreditAttribution: roball commented 29 August 2013 at 17:40

File	Size
customer-profile_-_billing_-_fields.png	39.06 KB

What is the machine name of your VAT Number type field in your Billing information profile type (or in the profile type you are using the VAT Number field)?

As shown in the attached screenshot, mine is called field_vat_id.