I thought I was having a similar problem but it was because of a misunderstanding of how the various 'Add Field' buttons work. Might this be your issue as well?
When you create a new Pod and go to add a field to it, you're presented with a form to define the field. There default options shown are:
- Field Type (Plain Text is selected by default)
- Options: (Required checkbox, unselected)
Below that (but aligned with the right side of the form) is a button saying 'Add Field'.
Below THAT is another row of headers "Label", "Name", "Field Type" and below that, another button named 'Add Field'.
It looks like the semantics for the two different 'Add Field' buttons are different (it might make sense to rename one of them).
The one associated with the form is the one that does the work of actually storing/saving the field, and the one below the bottom header line displays a new form for entering another field.
What I had been doing was, assuming that all the 'Add Field' buttons just displayed more blank field forms, filling in the data for the first field and then pressing 'Save Pod'.
But since I hadn't pressed the 'Add Field' button associated with my defined field, nothing was saved.
It's a bit confusing to have two different types of buttons on the same page that do two different things. Perhaps the one associated with the form (that does the actual saving of the field data) could be named 'Apply', or... 'Save Field' or something like that. Or find a different term for the one that just creates new blank forms to be filled in.
(from a UX perspective, it feels wrong to me that I have to explicitly save each field I have filled in AND then save the Pod itself to commit my changes - the inner form button seems superfluous - why wouldn't 'Save Pod' commit all the fields I have defined?)