Just noticed that a saved search was no longer working properly. Upon examining the Filter pop-up, I saw that one of the Search Rules was missing and quickly realized that it involved a field whose name I recently changed.
The search rule did not update itself to reflect the renamed field, so the rule basically referenced a field that didn’t exist any more. Easy to fix by adding back the search rule with the new field name.
Not sure if that would be considered a bug or a feature, but I thought it would be worth airing out so that people would be careful about renaming fields. I’m wondering if there would be similar issues if a calculation field refers to a field whose name is changed.
Thanks,
Mike
Unfortunately for Saved Searches, the way the NSPredicate code works, it’s based on the field name. But in Calculation fields I store the field’s internal ID, so if you rename a field that’s used in a Calculation it’s ok. Tap Forms will display whatever the current field name is. But not for Saved Searches.
.
