When showing related records, if there are multiple related records, FileMaker defaults to showing the first record. So if your relationship between the Appointment table occurrence and the Status table occurrence is sorted by the Date in descending order, then the first record will be the most recent status.
That totally worked. I created a Status Update field in the Appointments table that is the same as the Status update field in the Status table (Appointment::AppointmentStatusUpdate = Status::StatusUpdate). I then edited the relationship between the two tables so that the Status table is sorted by timestamp, in descending order. The StatusUpdate field in the Appointment table now shows the most recent update, and I can place that field on my report.
Glad to hear it worked.
By the way, you shouldn't need to create a field in the Appointments table. You should be able to reference the field from the Status table directly (since there is an established relationship between the two table occurrences). Or perhaps there is more going on with your database.
Might not have been necessary. Who knows!
I would encourage you to try to use the Status::StatusUpdate field directly to take advantage of FileMaker's relational database structure. Creating unnecessary, duplicate fields in another table can lead to issues in the long run and is not a good practice to get into.
There are cases when something like that is necessary or beneficial, but from what you've described, this doesn't seem to be one of them.
Just offering some friendly advice to help you make the most of FileMaker.