Change record status: 
Project: 
Introduced in branch: 
8.5.x
Introduced in version: 
8.5.x
Description: 

Previously, views data was wrongly assuming that all field level columns in views data were named like the base table. i.e. just the property name, like 'roles', or 'uid'. However, with multi-value base fields, all the field values are stored in their own ENTITY_TYPE__FIELD_NAME table. The suffixing of the field name was missing from the column in this case. E.g. The actual column name for the 'target_id' column in the 'users__roles' table would actually be 'roles_target_id' NOT 'target_id'. The generic entity views data handling now uses the actual storage column, rather than assuming the field name.

This will also remove duplicate handlers from views listings in some cases.

In rare cases this could break some existing views data. However, views_update_8500() updates the field names for views data in the views configuration. If you have an overidden handler that relies on overriding the old (broken) views data column name. Your code may need to be updated to use the actual storage name for the column.

Impacts: 
Site builders, administrators, editors
Updates Done (doc team, etc.)
Online documentation: 
Not done
Theming guide: 
Not done
Module developer documentation: 
Not done
Examples project: 
Not done
Coder Review: 
Not done
Coder Upgrade: 
Not done
Other: 
Other updates done