Support for Views Custom Table

The views API in Drupal is designed to work with content entities. And content entities only. ECA is using that API to receive a list of content entities to deal with them.

Sometimes, it's felt that this views API is a limitation that contrib modules try to overcome. There is one that also wants to make config entities available to views. It mostly works, but it breaks a lot as well. Doing some custom table enhancement sounds like pretty much the same issue.

I wonder if you couldn't define a custom entity type instead and load your data into the entity data table. That way, you would have full views support and no issue with any other component in Drupal that also follows APIs.

Thank you jurgen,

If you mean to create a content type in drupal with fields and use for example feeds module to load them - this would require additional step in between as vba cannot interact with drupal server directly to store for example json because of firewall, vpn and proxy in our case.
So we can use just mysql and using insert into table commands is quite difficult in drupal as it has many references and many tables as every field has 2x. This could be option but wanted to try any simplifier one thats why i wanted to use that views custom table one but did not expect that eca wont work with..

using insert into table commands is quite difficult in drupal as it has many references and many tables as every field has 2x

That's not correct. If you build your own entity type just with base fields, not in the UI but in code, then you get a single table with one column for each field. You can then easily import with mysql into that table and have full entity API support.

thank you,

Will try this method, it sounds less complicated.
I guess this can be closed.