UITable UITextField not displaying data correctly SWIFT 3.0 - swift

Question

My application code is pretty lengthly so I would like to try and get this problem resolved without having to show a bunch of code....but here is what is going on..
I have a tableview with dynamic cells all set up just fine. There is a textfield in the cell. When data is entered into the textfield, it is then sent to a label within that same cell. This happen when a "done" button is pressed. This all works just find until I have about 6 rows added to the table. At that point, when the "done" button is pressed, the data gets all mixed up. Sometimes the data is sent to the wrong cell label and other times it doesn't send at all. This only happens when I get to about 6 rows. I am very confused. The cells are displayed based on a Core Data entity.count...the textfield has the delegate set as itself....I have no clue what could be causing this...only after 6 rows!?
Thank you in advance for your help...like I said, I would like to try and avoid pasting my code here but if I have to provide some I will or I can talk you through what is going on in my code...
EDIT
Here is some of my code in cellForRowAt that deals with the textFields in the cell content
if searchResults.count > 1 {
if showInGrams {
if foods[indexPath.row].units != "g" && foods[indexPath.row].units != "grams" && foods[indexPath.row].units != "Grams" {
if cell.changeServingTextField.text == "" {
cell.labelServing.text = String(format: "%0.2f", (100 / foods[indexPath.row].coefficient) * searchResults[indexPath.row].doubleValue)
cell.labelUOM.text = "grams"
} else {
if cell.changeServingSegmentedControl.selectedSegmentIndex == 0 {
cell.labelServing.text = String(format: "%0.2f", Double(cell.changeServingTextField.text!)!)
cell.labelUOM.text = cell.changeServingSegmentedControl.titleForSegment(at: 0)
//show default values
} else {
cell.labelServing.text = String(format: "%0.2f", Double(cell.changeServingTextField.text!)!)
cell.labelUOM.text = cell.changeServingSegmentedControl.titleForSegment(at: 1)
}
}
} else {
if cell.changeServingTextField.text == "" {
cell.labelServing.text = String(format: "%0.2f", searchResults[indexPath.row].doubleValue * foods[indexPath.row].serving)
cell.labelUOM.text = "grams"
}
}
} else {
if cell.changeServingTextField.text == "" {
cell.labelServing.text = String(format: "%0.2f", searchResults[indexPath.row].doubleValue * foods[indexPath.row].serving)
cell.labelUOM.text = foods[indexPath.row].units
} else {
if cell.changeServingSegmentedControl.selectedSegmentIndex == 0 {
cell.labelServing.text = String(format: "%0.2f", Double(cell.changeServingTextField.text!)!)
cell.labelUOM.text = cell.changeServingSegmentedControl.titleForSegment(at: 0)
} else {
cell.labelServing.text = String(format: "%0.2f", Double(cell.changeServingTextField.text!)!)
cell.labelUOM.text = cell.changeServingSegmentedControl.titleForSegment(at: 1)
}
}
}
I hope this helps, thank you

Answer 1

What you are seeing is a symptom of UITableView's reuse strategy. May be what you want to do is store the information entered in your UITextField in a collection and then every time the tableView "reloads", you pick it out from that collection for the current indexPath and load it.

Answer 2

A line like this is never going to work:
if cell.changeServingTextField.text == ""
The problem is that cells are reused. Thus, in its previous life, if the text field had text, it still has text and the test will fail.
Instead, your logic needs to be based entirely on what row this is and what the data corresponding to that row is. And it needs to cover every case, because the cell can be reused.

Answer 3

Things would be clearer if you moved most of this logic into the cells themselves. You can start off by making all your cell's IBOutlets fileprivate and assigning a model object or dictionary as a property of the cell. That way you're separating the logic for creating the cells from their display - and will prevent you using cell's outlets to determine state.
While this might not solve your problem directly, separating the logic might clarify where to look.