Product and version: FMDataMigration 18.104.22.168
OS and version: macOS 10.13.5
In two separate solutions, we added a new field (number, foreign key) to an existing table and then migrated data from the previous version of the solution. After the migration, we populated the new field via a script. In both cases, no records would appear in a portal that used the new field as a foreign key. A find for any value that appeared in the field would return no records. Reindexing the field (either manually or via Recover) caused the records to appear in the portal and finds worked as expected.
How to replicate:
We have attempted to replicate in a new file without success, but the same scenario has occurred in two independent systems. None of the source or target files show any sign of corruption (recover reports no errors).
Workaround (if any):
Reindex fields after data migration.