The API attempts to write route names to the entity_id column that exceed its schema length, causing a write failure.
Create a view with a long nice name.
Changing to machine names would fix the problem but cause a lot of annoying data duplication to existing dashboards without writing a prohibitively complicated update hook. Better to just truncate the string for now; long strings don't fit in the dashboard UI anyway, and this field will eventually have to be rewritten as part of the dashboard initiative.
Compare API code and DB column lengths and truncate strings as needed.
I plan to be a little conservative on length, so some sites with entity types with exactly the character length limit may see a duplicate result in their dashboard for "View: My very long name for a view" and "View: My very long name for..."
Active
2.2
Bugs
Issue #3515376 by itmaybejj, alhepler: Dashboard sync fails for entity...
Automatically closed - issue fixed for 2 weeks with no activity.