Hello Kyle,
I already feared that this might be the case. Unfortunately I haven´t found a solution with K2, either.
BUT !!!
The delimiters might actually do the trick, at least for now until you guys come up with a better solution
Creating between 90 and 150 fields for 30 Projects is kind of a boring job
I actually got this to work, but now I have another problem.
I put the delimiters inside a table with four columns and just one row, so that I don´t have to worry about empty rows if values are not filled in, and it´s at least somehow formatted.
The single fields are unpublished so they don´t appear on the front end in addition to the list that contains the delimiter fields.
But now when I want to edit the fields via "update profile" the table containing the delimiters is still there, instead of the fields with the values.
I´m just re-publishing the fields atm so that they only show up in the backend/on "update profile", with the table automatically being pushed down by the now-present fields.
Any ideas on how to solve this more elegantly?
Thanks,
Michael