New List on Existing table doesn't create all the fields...

[nickbunyan]

I am trying to use Fabrik to display a view of an existing DB table. As it happens this is a CB profile table, with 40 fields.

When I create a new Fabrik list using 'Existing DB table...' it creates 34 fields only and ignores the other 6. I can see no reason why Fabrik should barf over the final 6 fields.

I have tried reordering the fields within the Table manually through SQL but it still appears to 'select' the same 34 elements.

I am at a complete loss so any advice would be much appreciated.

FYI - the table being referred to does actually contain 40 elements when viewed through HeidiSQL.

 

[troester]

I assume those fields have a different column type (e.g. float).
It seems Fabrik takes only fields with column types defined in Fabrik Options.

But you can add them manually:
add an element, exactly the same NAME as in the database, choose appropriate plugin and settings (e.g. if DB column is float choose plugin "field" with Formatting/Format "decimal")

 

[nickbunyan]

Hi troester. Thanks for the feedback. Sadly, although I can add additional fields by hand as you say - it is NOT the field type that is causing the problem. In the screenshot below, the

fields efamember and efastatus get created, but the fields rfamember and rfastatus do not. They are clearly the same field types so there is a bug in there somewhere, or something else is going wrong.

I also have a couple of very large tables to work with and creating fields by hand is time-wasting at the very least. Any additional suggestions welcomed...

 

[troester]

Yes, I think it's a bug somewhere.
I could replicate a missing element with a "float" column, so this seems to be one issue (but not yours)
https://github.com/Fabrik/fabrik/issues/1034

Are all elements after the "MEDIUMTEXT" missing?
Maybe this is breaking something (because of empty size...)

 

[nickbunyan]

The MEDIUMTEXT element can not be the problem because there is one earlier in the list which is exactly the same and gets created ok... but I will take a look at the other thread for info.
I also tried re-arranging the element order using SQL within the original table, and it still seemed to barf at 34 elements... Will try and test more later.