Fluid fields that share custom fields wields unexpected behavior
Developer Preview
For each channel_data_field_x table that references a field inside a Fluid field, the entry_id column remains 0 when saving an entry, rather than referencing the entry ID itself. This does happen in the channel_data_field_x table that references the Fluid field itself.
Also, not referring to the Fluid field ID in the aforementioned tables implies that having 2 Fluid fields in one channel (entry) is not possible, while we are able to create multiple per channel.-
Disregard the above, the issue is described below.
I also noticed that if you do have multiple Fluid fields in a channel, and both contain the same custom field, then when you add a row of that field, you get 2 instances. Also, the data will be saved as an instance for the 1st fluid field (which is probably due to the above DB schema issue).
Thanks for catching this Low. I’ve got a fix in for the next release.