Follow the link
to the right person.

Build and compare

• Preserve the latest saved Lesson 4 file, portal view and Overdue fix.
• Open contact button in the overview Body, using its UI handler.
• Controller: expected layout and task, validated commit, related-contact guard, navigation, immediate error check.
• Go to Related Record: Contacts; explicit Contact Task Views layout; show only related records; current record only; same window.
• Keep all earlier scripts, data and relationships unchanged.

Test in a disposable copy

1. Use a disposable practice copy. Open Follow-up Overview in Browse mode, List View. Click All tasks and note the task found-set count.
2. On Alex Morgan’s “Send project outline” row, click Open contact. Expect Contact Task Views showing Alex Morgan and alex.m@example.com. The destination toolbar counts Contacts and should show one related contact in its found set.
3. Click Tasks to return. On an Alex Rivera task row, click Open contact. Expect Rivera and alex.r@example.com. The shared first name Alex must not affect the result.
4. On the contact layout, choose All and Apply view to compare that contact’s tasks. Choose Open and Apply view. Rivera may have no matching Open tasks; that does not mean the contact or its Done tasks disappeared.
5. On Contact Task Views use the toolbar’s Show All to restore all contacts. Return with Tasks. On the overview click Open tasks, then open Morgan and return again. Confirm the task found set remains the Open result. All tasks restores the full task list.
6. In a disposable copy, clear a task’s required Task text and click Open contact. Expect a save/validation message and no navigation. Restore the text and commit.
7. Test a missing link only in a disposable copy: on the Follow-up List table, temporarily display FollowUps::ContactID using Modify, copy one task’s original value into a temporary note, and replace it with a unique test value such as missing-contact-test. Commit, return to Follow-up Overview, and click that row’s Open contact. Expect a message and no navigation. Restore the exact original ContactID and verify the link, or discard the entire practice copy. Never edit Contacts::PrimaryKey or do this in your main file.
8. In a disposable copy, set all tasks to Done and run Open tasks. Expect the existing no-matches message and no Body row buttons. Recover with All tasks; discard this test copy afterward.
9. Check that each Open contact button fits beside the Overdue cue and opens its own row. Check existing portal entry/completion, navigation, searches and report return. Save, close and reopen; repeat the Morgan/Rivera navigation checks.

Explain what you learned

Why do the two contacts named Alex need an ID-based relationship?

Why does 1 / 4 Found on the contact screen not mean three contacts were deleted?

Why stop after a missing link or a navigation error?

Your notes and questions